Triage: Confusion between action and executable command handlers #938
Description
There is a silent change in behaviour based on whether a description parameter is added to the .command definition. This is a common cause of confusion. Opened this issue to collect the related issues found during triage.
Issues:
- Having a lot of difficulty getting nested commands #511 Having a lot of difficulty getting nested commands
- Subcommand not registered if no description provided during the setup #633 Subcommand not registered if no description provided during the setup
- executeSubCommand() shouldn't be called if I provide action #706 executeSubCommand() shouldn't be called if I provide action
- Specifying command description forces lookup of command in separate file #715 Specifying command description forces lookup of command in separate file
- Handle git-style commands programmatically #767 Handle git-style commands programmatically
- Having multiple commands with .action() fires all of the command's actions. #770 Having multiple commands with .action() fires all of the command's actions.
- Make it clear that you can't pipe action to command that was invoked with description #776 Make it clear that you can't pipe action to command that was invoked with description
- (1) does not exist, try --help #786 (1) does not exist, try --help
- I use "yyy" command in any "xxx" file,there will be a error: con't find module "/path/to/xxx-yyy" #815 I use "yyy" command in any "xxx" file,there will be a error: con't find module "/path/to/xxx-yyy"
- Commander always executes the first registered command #825 Commander always executes the first registered command
- Passing description to the "command()" method causes error being produced in runtime #976 Passing description to the "command()" method causes error being produced in runtime
Pull Requests:
- invoke git-style sub commands only when required #810 invoke git-style sub commands only when required