This repository was archived by the owner on Oct 20, 2024. It is now read-only.
Adjust the opt-out behavior of CLI flags #350
Labels
enhancement
New feature or request
Comments
|
The problem I see with npx @svelte-add/tailwindcss@latest --typography --formsis that this npx @svelte-add/tailwindcss@latestwould implicitly assume that all options are false / fallback to the default value and that this would not trigger the interactive cli. That's why I would currently prefer the your suggested alternative, although I'm not sure if |
|
Agreed, |
8000
|
Please do not consider working on this until #368 is merged, as it was necessary to rewrite major amounts of the |
|
unblocked |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Topic
applies to all adders
Description
It would be preferable if the CLI flags were designed to be opt-in rather than opt-out.
One can imagine that when a couple of more plugins are added, it would quickly become cumbersome to add all of these opt-out flags just to avoid the CLI wizard:
Describe the solution you'd like
Instead, it should be the inverse, where adding the flag includes the addon/plugin:
Alternative
An alternative could be to include a
--noneflag to preserve the default state of running through the CLI wizard, but also not having to add all of the flags to avoid it either:The text was updated successfully, but these errors were encountered: