Replies: 7 comments 2 replies
-
|
@rawkode 2 notes on the list above:
|
Beta Was this translation helpful? Give feedback.
-
|
Good call |
Beta Was this translation helpful? Give feedback.
-
|
Would love some feedback from @icepuma @kraileth @bketelsen @nunix @sidpalas @svallory @mt-inside @Spazzy757 @vielmetti @martintc |
Beta Was this translation helpful? Give feedback.
-
|
When moving towards subcommands I recommend using Every subcommand to inspect the environment of |
Beta Was this translation helpful? Give feedback.
-
|
yes, most of those look very useful. I think subcommands are the only way to expand the functionality without getting caught up in a sea of flags. Ick. |
Beta Was this translation helpful? Give feedback.
-
|
I'd prefer an approach with commands to one that had lots of flags, all things considered. Especially if the flags all support some kind of "help" subcommand. |
Beta Was this translation helpful? Give feedback.
-
|
OK. I'll get subcommand support added over the next two weeks. Thanks for your feedback, everyone. |
Beta Was this translation helpful? Give feedback.
-
|
really nice addition, and concerning subcommands, as I saw it for This would avoid some breaking changes later on |
Beta Was this translation helpful? Give feedback.
-
|
+1 for subcommands, some that are really required:
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
At the moment,
./comtryaonly performs a single command: run manifests.We accept a few flags that can change this behaviour, but there's no concept of a subcommand.
Before we move towards 1.0, we should definitely have the discussion around this behaviour.
Do we see a world with:
Beta Was this translation helpful? Give feedback.
All reactions