Skip to content

Adding options cssClassTabsLi and cssClassTabsA #73

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

robsdedude
Copy link

See my comment here.
These options make using this nice widget much easier with BootStrap4. I've also included a new example in run to demonstrate and test this.

One thing: Since bower does not support multiple versions of the same dependency (at least I couldn't find out how), I'm afraid the example in run will not work when the libs are installed using bower. Generally I couldn't quite find out how bower is supposed to act in this repo.

@robsdedude
Copy link
Author

If this pull request gets merged I'd like to submit another one that outlines the steps to use this lib with BS4 in the README.

package.json Outdated
@@ -20,6 +20,7 @@
],
"dependencies": {
"bootstrap": "^3.1.1",
"bootstrap4": "npm:bootstrap@^4.3.1",
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this. I wouldn't want to introduce BS4 as a dependency for current users who are only using BS3.

Copy link
Author

@robsdedude robsdedude Oct 8, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can. But it'll break the demo in run. So I'd have to remove it as well.

Maybe the demos should have their own dependencies?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I moved it to the dev dependencies. How do you like that approach?

also adjusted dependencies:
bootstrap 3 || 4 for the lib
and bs3 AND bs4 as dev dependencies for the demos
Copy link
Owner

@mikejacobson mikejacobson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a few comments. Thanks for all the work! Overall it looks really good. You obviously put a lot of effort into this.

typeof jQuery.fn.tab.Constructor === 'undefined' ||
typeof jQuery.fn.tab.Constructor.VERSION === 'undefined') {
throw new Error("jquery-bootstrap-scrolling-tabs requires Bootstrap's tab plugin for jQuery");
}
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please remove this error checking code, both blocks. I trust the developer to have their tabs working correctly before trying to add this plugin. Also, the second block, checking for the tab plugin, as written seems to break some versions of BS3 that don't include the constructor VERSION. Both of the demo plunks threw errors because of that.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The problem with 3 as default without a means to check if 4 is installed is that "dependencies": { "bootstrap": "^3.1.1 || ^4.3.1", …} will cause the package manager to install bs4 unless the developer installed bs3 before. So I think it's problematic to choose 3 as default while the package manager by default will install 4.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about I remove the check if BS exists but try to find jQuery.fn.tab.Constructor.VERSION and if it exists I use this version as default. If it doesn't exist I'll use 3.

@robsdedude
Copy link
Author

Ok. Please check my comments and latest changes. I'll leave the PR as is. I'd be happy if you were able to take it from here (shouldn't be much work left to be done).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants