Css Important option #32
Open
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.
I am currently integrating Tailwind.css into an existing website. Tailwind allows you to specify an
importantoption in its configuration which makes all of their style declarations include the!importantflag. See documentation here.This is very useful when transitioning an existing project to Tailwind so that the new styles will override existing style sheets. I was also attempting to use this library in that same project, but was finding that the styles being applied weren't working because sometimes they were getting overridden by Tailwind styles.
This PR allows for a
cssImportantoption which simply adds the!importantflag to the plugin's generated css. After adding this option, the plugin worked great even with Tailwind'simportantstyles in place.