These are chat archives for kbknapp/clap-rs

31st
May 2017
Nick Mosher
@nicholastmosher
May 31 2017 17:24
I just noticed that you've given an ArgGroup struct for categorizing arguments, could it be beneficial to also provide SubcommandGroups? I'm thinking for an application that has a large interface, it could be advantageous to be able to group help messages based on the group the command belongs to.
Kevin K.
@kbknapp
May 31 2017 17:27
Perhaps, although aliases usually fit that bill pretty well
Nick Mosher
@nicholastmosher
May 31 2017 17:27
Oh, where are those?
They can also be defined for args
Unlike args, subcommand groups wouldn't make sense in the "you must use one of these, or you must use only one from this group" because subcommands inherently work that way
Nick Mosher
@nicholastmosher
May 31 2017 17:30
I see. I guess the use-case I'm getting at isn't analagous to ArgGroups, it's more for the help messages. Could there be a way to dictate how the commands are listed in the help menu? For example, if my app has 50 subcommands, could I group them into 10s that are more related?
Kevin K.
@kbknapp
May 31 2017 17:32
Ah are you talking about grouping them visually?
There's an issue open for that
kbknapp/clap-rs#805
Is that similar to what you're thinking?
Nick Mosher
@nicholastmosher
May 31 2017 17:34
I believe so... I'll need to read it in depth. I should have gone looking for that in the first place :P
Kevin K.
@kbknapp
May 31 2017 17:36
No worries! If it's not what you mean I'm not against the idea, I just need a use case to support so I can see exactly how to do it
Which is hard to see through chat sometimes :P
Nick Mosher
@nicholastmosher
May 31 2017 17:37
Yeah, I totally understand. I might end up putting a more detailed post of my use-case on one of the open issues if it's relevant enough. Otherwise I may open a new issue
Kevin K.
@kbknapp
May 31 2017 17:37
:+1: