SubCommand seems not required to be declared again as a parameter type.
See original GitHub issuemaybe new ArrayList<>();
is OK.
protected static final List<SubCommand> SUB_COMMANDS = new ArrayList<SubCommand>();
Issue Analytics
- State:
- Created a year ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
SubCommand seems not required to be declared again as a ...
SubCommand seems not required to be declared again as a parameter type.
Read more >Options disallow values that match subcommand name #1125
Some apps may want to allow such values only if it was "attached" to the option with a = or : separator. (E.g.,...
Read more >Invoking another subcommand with Python click doesn't seem ...
This checking is done when parsing the parameters. If you are calling ctx.invoke() directly it is expected you understand what your command ...
Read more >SIte subcommand—Send site-specific information to a host - IBM
Specifying DATAClass with no parameter value cancels the data class specification. The equal sign (=) is optional in this case.
Read more >Commands and Groups — Click Documentation (8.1.x)
Click strictly separates parameters between commands and subcommands. What this means is that options and arguments for a specific command have to be ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Please assigned it to me, i want to try it.
please assigned it to me, i want to try it.