Can clap generate usage help text for nested optional arguments?

[cytrinox]

I need a lot of commands like app get [PATH [ATTR]]. I can instruct clap that ATTR requires the PATH argument, but the usage help text is generated like app get [PATH] [ATTR]].
Any chance to change this behavior?

[epage]

Clap's positional arguments, generally have a requirement on the previous positional argument (there are some rare exceptions).

Despite that, we always render the usage as [PATH] [ATTR]. We do this also for option values (--flag [PATH] [ATTR])

I've considered being more explicit / strict about this with [PATH [ATTR]]. However, I feel like the intent is still fairly clear and I'm concerned that too much nesting would make it harder to read the values.

[tmccombs]

I'm not sure what the best way to handle this is, but with fd we've had multiple users confused by this, and think that with
fd [OPTIONS] [pattern] [path]..., if you only supply a single argument, it is the path, not the pattern.

Another, alternative could be if I split the usage up to look like:

Usage: fd [OPTIONS] <pattern> [path]...
   or: fd [OPTIONS]

but it sounds like you don't want to support that either.

[epage]

That is from many years ago and from a different maintainer.

Some existing related issues are:

• Not obvious how to provide multiple usage statements with App::override_usage() #3413
• Context-Aware Multiple Usage from Argument Groups #4191