Tweak internal CSS AST implementation #1512
Draft
Conversation
This file contains hidden or 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
How this prints will be dependent on Tailwind CSS version. Since we don’t know what version that is yet we’ll set up a simple toggle that we can flip after (eventually) threading version information through.
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.
Right now our CSS AST doesn't differentiate at-rules with an empty body and at-rules that have no body at all.
This is normally not a problem however for CSS mixins
@apply --foo;and@apply --foo {};mean different things — this requires us to be able to differentiate them. We'll be changing this in Tailwind CSS itself at some point so I'm changing this here to be forward compatible with those changes.