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 when handling subcommands using separate meow instances like this:
constbar=argv=>{constcli=meow({
argv,help: ` Usage $ foo bar <input> `});};constcli=meow(` Usage $ foo <command> Commands bar`);// Check cli.input and handle commands
If the user enters $ foo bar --help they get the help for foo and not foo bar
There's a wrapper called moggie that handles subcommands, but I was thinking we could to add a commands: [commands] option to meow so it doesn't block the --help flag?
Meow could either:
Not show help if a command is matched, leaving everything else to the user to handle
Handle the argv filtering and return the matched command and filtered argv
I'm happy to write something and submit a PR.
The text was updated successfully, but these errors were encountered:
Running into this issue now. A subcommand implements it's own meow instance with it's own help text. Not using moggie.
Rather than providing a list of commands to meow, since that is a moggie-specific solution, maybe provide a toggle to turn off the automatic --help handler? The programmer could then handle how and when showHelp() is called.
I could submit a PR if necessary. Unless there is a better way to handle this with the existing options in meow or minimist?
Currently when handling subcommands using separate meow instances like this:
If the user enters
$ foo bar --help
they get the help forfoo
and notfoo bar
There's a wrapper called moggie that handles subcommands, but I was thinking we could to add a
commands: [commands]
option to meow so it doesn't block the --help flag?Meow could either:
I'm happy to write something and submit a PR.
The text was updated successfully, but these errors were encountered: