fix: default subcommand argument behavior #365
Merged
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.
This PR fixed the behavior of which default subcommand runs and what arguments get passed to it. With this fix, if a valid group is provided that has a default subcommand, it will always run the default subcommand in that group and will only strip away one argument, the group name. If no valid group or subcommand is given but a top level default subcommand exists, the top level default will run and no arguments will be removed. Below is an example and the code used to generate it.
Example screenshot
Test command file used
This PR closes #351