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.