Fix issue with tailwind class escaping #32
Merged
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
NeusFear
approved these changes
Dec 9, 2021
|
Please merge this! |
|
Looks good! Thanks! |
adoxography
added a commit
that referenced
this pull request
Mar 20, 2023
Fix issue with tailwind class escaping
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.
tailwind.ewas being used incorrectly, causing classnames to be incorrectly escaped. This caused@applyto not work. I believe this is what causes #25See below for the generated css:
The input for
tailwind.eneeds to be the whole class name. Prior to this PR, the input was only the colour modifier (100, 200, 300, ect). As classnames cannot begin with a number, this gets escaped.