[examples] Add new Tailwind CSS Prettier plugin to example #33614
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
ecklf
requested review from
ijjk,
leerob,
shuding,
steven-tey and
timneutkens
as code owners
leerob
approved these changes
Jan 24, 2022
leerob
changed the title
This was referenced Jan 27, 2022
1 task
kodiakhq bot
pushed a commit
that referenced
this pull request
Feb 5, 2022
## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` --- I'm getting this warning when running `yarn lint` on the local:  After a quick check, it is caused by the `tailwindConfig` option in the `prettier.config.js` file, added in PR #33614 I guess the reason is because the workspace does not install that plugin. We can safely remove that option in the example, because it's already [the default location](https://github.com/tailwindlabs/prettier-plugin-tailwindcss): > By default the plugin will look for this file in the same directory as your Prettier configuration file. However, if your Tailwind configuration is somewhere else, you can specify this using the tailwindConfig option in your Prettier configuration.  The warning is gone after removing that option.
natew
pushed a commit
to natew/next.js
that referenced
this pull request
Feb 16, 2022
) ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` This PR adds the new official plugin for class sorting from Tailwind Labs to the Tailwind example. Rel: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier
natew
pushed a commit
to natew/next.js
that referenced
this pull request
Feb 16, 2022
…#34019) ## Documentation / Examples - [x] Make sure the linting passes by running `yarn lint` --- I'm getting this warning when running `yarn lint` on the local:  After a quick check, it is caused by the `tailwindConfig` option in the `prettier.config.js` file, added in PR vercel#33614 I guess the reason is because the workspace does not install that plugin. We can safely remove that option in the example, because it's already [the default location](https://github.com/tailwindlabs/prettier-plugin-tailwindcss): > By default the plugin will look for this file in the same directory as your Prettier configuration file. However, if your Tailwind configuration is somewhere else, you can specify this using the tailwindConfig option in your Prettier configuration.  The warning is gone after removing that option.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Documentation / Examples
yarn lintThis PR adds the new official plugin for class sorting from Tailwind Labs to the Tailwind example.
Rel: https://tailwindcss.com/blog/automatic-class-sorting-with-prettier