-
-
Notifications
You must be signed in to change notification settings - Fork 172
Support regex matches for attributes and function names #405
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
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
Co-authored-by: Robin Malfait <[email protected]>
Thanks! |
Thank you guys! |
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.
This PR adds support for using regular expressions in both the
tailwindAttributes
andtailwindFunctions
options. Regular expression patterns must be wrapped in strings as Prettier itself does not support regex literals for options (since all Prettier options are representable as JSON).Here's an example that considers:
classList
orstyleList
Before (HTML):
After (HTML):
Before (JSX):
After (JSX):
Before (JS):
After (JS):
And exact matches still work as they did before and can also be combined with regex patterns:
Before (HTML):
After (HTML):
Framework Support
Just like with existing static attributes we automatically generate regex patterns that match Vue and Angular attribute bindings.
/data-.*/
will also match:data-*="…"
andv-bind:data-*="…"
/data-.*/
will also match[data-*]="…"
Closes #399
Fixes #373