Fix for [Doubly nested subcommand creates wrong help output] #755
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Related this issue #627. If we don't put command name (basename) there, it makes sense as arguments after the command. Since it seems to take time to get subcommand names there, I think it's the solution for now.
|
@KishiTheMechanic can you add a test for this behavior so we can validate it works as expected? |
Closed
|
Little bit late on that, but I monkeypatched that here if somebody else has that issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related this issue #627.
If we don't put command name (basename) there, it makes sense as arguments after the command.
Since it seems to take time to get subcommand names there, I think it's the solution for now.