-
-
Notifications
You must be signed in to change notification settings - Fork 384
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
Add vscode tailwind extensions & prettier tailwind linter, sort tailwind classes #4622
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
Can we add linting as well then? Not everybody uses VSCode. |
pat-s
changed the title
Add vscode tailwind extensions
Add vscode tailwind extensions & prettier tailwind linter, sort tailwind classes
Dec 26, 2024
Deployment of preview was torn down |
anbraten
reviewed
Dec 27, 2024
anbraten
reviewed
Dec 27, 2024
qwerty287
reviewed
Dec 27, 2024
pat-s
force-pushed
the
chore/tailwind-extensions
branch
from
December 29, 2024 14:56
7693e71
to
f80dcc1
Compare
pat-s
force-pushed
the
chore/tailwind-extensions
branch
from
December 29, 2024 15:05
f80dcc1
to
658ece1
Compare
xoxys
approved these changes
Dec 31, 2024
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.
These are the ones that cause the auto-sorting in all my recent PRs. If we would all use these (and sort all classes once), we'd have a predictable and consistent order of tailwind classes.
docs/
andweb/
enforcing the sorting. As the release process inplugin-prettier
has some issues currently, I've used:next
to move on