lessen restrictions on class names to support tailwindcss styling #45
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
ryanbalsdon
force-pushed
the
more-classes
branch
from
3beb64e to
4a0ab8d
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #42
It looks like there are two very different grammars defined against class names for CSS and for HTML. Where CSS restricts most special characters, HTML only restricts whitespace characters (because it's a space-separated list).
This patch switches the class name validation to use HTML-style, anything-goes class names (that have no spaces). These non-CSS-compliant class names can still be used from within Javascript and are used heavily by TailwindCSS.