Flag Groups

[cpuguy83]

It might be nice to be able to have command.Flags be a [][]Flag for the purposes of being able to group flags in the command help output.
In addition instead of a straight up [][]Flag, a new FlagGroup struct type may be better, where we can define a name/other fields.

WDYT?

[jszwedko]

I think it would be nice to be able to group flags, but I also wouldn't want to create overhead for, what I'm guessing is, the majority case that doesn't need to group their flags.

What might be better is making the library more flexible such that additional properties could be assigned to flags and then custom help templates could be created that organize them.

[hickeng]

@jszwedko a mechanism like the command categories would do nicely. In fact I thought categories were for flags originally having read the docs too quickly.
IMO there are likely to be three distinct styles of CLI use where grouping is important:

1. lots of sub commands, few flags per command
2. few commands, large number of flags per command
3. lots of commands, large number of flags per command

IMO (2) and (3) are likely to be were most of the complexity lies, particularly if you have overlapping sets of flags that are shared between commands, meaning even lexical ordering of related arguments is problematic.

[jszwedko]

👍 I tend to agree now -- I'd be open to a PR that introduced the analogous category functionality to flags that exists for commands.

[michaeljs1990]

#796 adds this functionality for those who want to use it.

[coilysiren]

This feature is now in review - @urfave/cli please add a 👍 or 👎 to the top post if you're in favor or against this feature being added!

[stale]

This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else.

[coilysiren]

This looks like its still in limbo pending more interest?

[stale]

This issue or PR has been bumped and is no longer marked as stale! Feel free to bump it again in the future, if it's still relevant.

[AkihiroSuda]

What's current status?
#796 seems closed due to inactivity.

[coilysiren]

What's current status?

To expand on my comment 9 days ago, this issue is waiting on someone interested in refining the proposal and advocating for it 🙂 You are free to do that, if you are so inclined.

#796 seems closed due to inactivity.

Yes, if you would like to restart the activity there then you are free to do so!

[stale]

This issue or PR has been automatically marked as stale because it has not had recent activity. Please add a comment bumping this if you're still interested in it's resolution! Thanks for your help, please let us know if you need anything else.

[stale]

Closing this as it has become stale.