You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently it's not possible to have subcommands and arbitrary arguments on the same command. Like a "default" or "catch all" subcommand that will receive the args, if no subcommand was matched.
One use case would be to have the root command working with files (thus arbitrary arguments), but also have some subcommands like version. Instead, I would have to add a new subcommand to root that would take the files args, which adds unnecessary typing when using it.
The text was updated successfully, but these errors were encountered:
PR #284 supports this behaviour. Setting any Args validator would skip legacyArgs() behaviour of not allowing both args and subcommands on the root command.
Currently it's not possible to have subcommands and arbitrary arguments on the same command. Like a "default" or "catch all" subcommand that will receive the args, if no subcommand was matched.
One use case would be to have the root command working with files (thus arbitrary arguments), but also have some subcommands like
version
. Instead, I would have to add a new subcommand to root that would take the files args, which adds unnecessary typing when using it.The text was updated successfully, but these errors were encountered: