-
-
Notifications
You must be signed in to change notification settings - Fork 8.5k
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
RFC: better swizzle cli #2984
Comments
To facilitate the use of the users, when a user pass a command that don't exist in the CLI, we could output a help, showing the current options. Loved the idea. |
@slorber I will be interested if the issue is available. |
thanks You can probably start a poc, but there's ongoing work by @SamChou19815 that we should probably merge first here: #2671 |
@slorber I am working on this issue |
@slorber I was trying to get package name for themes but due to the use of |
hey @anshulrgoyal , maybe from the module path you could read the package.json in it, to get the name attribute? |
Did same in my pr. |
@slorber we should close this |
🚀 Feature
The swizzle cli experience works, but is a but rough and could be improved
Pitch
Here I'm using
yarn workspace docusaurus-2-website swizzle ...
in the screeshots (as I'm using D2 website for testing), but replace in your mind withyarn swizzle ...
Here are some suggestions
Display all the installed theme names with
yarn swizzle
, instead of:On theme name typo, better error with theme name suggestions:
Do not swizzle the whole theme files with
yarn swizzle @docusaurus/theme-classic
, insead display available names to swizzle. (breaking change)Typo on swizzle component name: same as theme, suggest valid names instead o:
Allow swizzling the whole theme files with an
--all
option:yarn swizzle @docusaurus/theme-classic --all
The text was updated successfully, but these errors were encountered: