Feature-Branch: Bootstrap Removal from OSS components #390
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.
What does this PR do?
This is the base branch for bootstrap removal on OSS-component , starting with the addage of the less reset file ( with cleanup of the reset added with *{ selector } )
& the removal of the bootstrap css import.
This is the backbone of the whole "feature" in which I will merge all other component removals , starting with upf-slider & the enable-popover modifier.
Related to: #
https://linear.app/upfluence/issue/VEL-2373/cleanup-oss-components-from-bootstrap
What are the observable changes?
aside from the reworked popover & slider components, the idea is that the transition should be seemless
Good PR checklist