You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 1, 2022. It is now read-only.
Comment by kbknapp Wednesday Feb 14, 2018 at 18:58 GMT
Totally agree this is a lacking feature, thanks for the suggestion!
In order for me to actually get v3 released I have to put blinders on and only implement bug fixes or super trivial features which are simple to forward port to the v3 branch.
I don't know that this is one such issue. I'll leave it open for v3 as it is something I do want to have.
Having said all this, if someone implements this for v2 I'm not against the PR, so long as the understanding is that for v3 I may have to rip out the commit and re-do it depending how deep into the internals it gets to implement this. (for v3 the internals are quite different, so some changes aren't trivial to forward port).
Comment by pksunkara Friday Oct 09, 2020 at 17:33 GMT
To solve this, we would either need to add a global_help_template function that would forward the template to children (example) or we could add a setting called PropagateTemplate which does the same.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Issue by ascclemens
Wednesday Feb 14, 2018 at 17:46 GMT
Originally opened as clap-rs/clap#1184
Affected Version of clap
2.29.4
Expected Behavior Summary
Being able to call
global_template
and have the template propagate down to subcommands.Actual Behavior Summary
For every single subcommand, I have to add a
template
call to get them all to match my custom template.The text was updated successfully, but these errors were encountered: