fix(nextjs): adding "none" style option to next component generator #15990
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
The React component generator has the option to choose "none" as a style option, particularly useful when using Tailwind. The Next.js component generator omits this option, even though the underlying React component generator allows it. This updates the generator schema to expose "none" as an option.
ashley-hunter
requested review from
ndcunningham,
jaysoo and
xiongemi
as code owners
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
xiongemi
approved these changes
Mar 31, 2023
|
This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request. |
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.
The React component generator has the option to choose "none" as a style option, particularly useful when using Tailwind. The Next.js component generator omits this option, even though the underlying React component generator allows it. This updates the generator schema to expose "none" as an option.
Current Behavior
There is a "none" style option for the React component generator, but not the Next.js component generator.
Expected Behavior
"None" should be supported in the Next.js generator.
Related Issue(s)
Fixes #