Closed deepyaman closed 4 months ago
Hi @deepyaman , Thanks for this. This looks awesome !
[Nit] I understand from the docs that --help will now show (*) infront of the default command. I am wondering if this confuses someone who does not have clear understanding of what this means. Should we implement a class which lists the commands ?
Hi @deepyaman , Thanks for this. This looks awesome !
[Nit] I understand from the docs that --help will now show (*) infront of the default command. I am wondering if this confuses someone who does not have clear understanding of what this means. Should we implement a class which lists the commands ?
I noticed that. I think it's very likely it could be a non-issue, in which case I don't think it needs to be over engineered.
If we want to remove the mark, or use something more explicit like (default)
instead of *
, we could extend DefaultGroup
to handle a default_cmd_mark
parameter, which would get passed to https://github.com/click-contrib/click-default-group/blob/main/click_default_group.py#L100.
If we want to remove the mark, or use something more explicit like
(default)
instead of*
, we could extendDefaultGroup
to handle adefault_cmd_mark
parameter, which would get passed to https://github.com/click-contrib/click-default-group/blob/main/click_default_group.py#L100.
Merged, but just let me know if want to do this; happy to slot it in quickly!
If we want to remove the mark, or use something more explicit like
(default)
instead of*
, we could extendDefaultGroup
to handle adefault_cmd_mark
parameter, which would get passed to https://github.com/click-contrib/click-default-group/blob/main/click_default_group.py#L100.Merged, but just let me know if want to do this; happy to slot it in quickly!
I don't see as a blocker for now. If it is a quick fix, we can say (default) which is much clearer. But I am happy to hear from @rashidakanchwala . Thank you
Description
Closes #1789
Development notes
QA notes
Checklist
RELEASE.md
file