Various Bootstrap-version JS generation fixes #548
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current state, Core UI Bootstrap JS is not really Bootstrap compatible.
All data attributes are expected to be data-coreui instead of data-bs, as with Bootstrap. This basically breaked a lot of Boostrap code.
Fixed this. Basically, with my fixes, CoreUI Bootstrap version becomes more or less 100% drop-in Bootstrap replacement.
Also fixed coreui.io website being written wrong in the source as bs.io.
Not in the least, the coreui -> bs replace was made only for the bundle versions. The regular Boostrap (non-Popper bundled) version was totally avoided.