Skip to content
New issue

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

Usage for command should include parent commands #739

Closed
mojavelinux opened this issue Jan 5, 2018 · 3 comments
Closed

Usage for command should include parent commands #739

mojavelinux opened this issue Jan 5, 2018 · 3 comments

Comments

@mojavelinux
Copy link
Contributor

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:

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.

@privateOmega
Copy link

Please merge this.

@shadowspawn
Copy link
Collaborator

This issue will be resolved when v3.0.0 is released. Available now as a prerelease. See #1001

@shadowspawn
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants