We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The usage for an action-based (sub)command is misleading. It seems to suggest that the command can be used by itself, without the parent.
For example, if we were making the git cli with commander.js, the usage for add would look like:
add
Usage: add [options] <pathspec>
However, it should show the parent command (the context) as well:
Usage: git add [options] <pathspec>
I guess if it's an executable it's fine, so this just applies to subcommands that are not executables.
The text was updated successfully, but these errors were encountered:
Please merge this.
Sorry, something went wrong.
This issue will be resolved when v3.0.0 is released. Available now as a prerelease. See #1001
2365feb
Shipped in v3 (thanks @mojavelinux): https://github.com/tj/commander.js/releases/tag/v3.0.0
No branches or pull requests
The usage for an action-based (sub)command is misleading. It seems to suggest that the command can be used by itself, without the parent.
For example, if we were making the git cli with commander.js, the usage for
add
would look like:However, it should show the parent command (the context) as well:
I guess if it's an executable it's fine, so this just applies to subcommands that are not executables.
The text was updated successfully, but these errors were encountered: