Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I've been experimenting with an alternative approach to PR# 205 for adding
subcommands
support. My favorite feature ofmeow
is the objects as configuration convention forflags
and I was interested in exploring how to carry over that pattern forsubcommands
. I'm pretty satisfied with the POC and would love some initial feedback before I continue iterating and moving this PR out of draft.Key features:
subcommands
subcommands
subcommands
use the existingmeow.options
properties to keep the API minimal, extensible, and familiar--help
(withautoHelp: true
) automatically shows the help text for the currentsubcommand
allowParentFlags
option is introduced to restrict top leveloptions.flags
from being used with a givensubcommand
cli.command
) containing the inputargs
of thesubcommand
and a reference to the resolvedsubcommand
s optionsHere is a subset of the proposed API! Though, I recommend pulling down the branch and testing out
barista.js
with the provided examples.