Is there any documentation for how to use dynamic completions under the 'unstable-dynamic' feature flag?

[vermiculus]

I recognize that the unstable-dynamic feature is very explicitly unstable, but I'd like to give it a try anyway and see what I find. This is pretty difficult to do though without documentation beyond examples/dynamic.rs.

Is there anything out there, official or not, that goes through this? In an ideal world, I'd like to have static completions for most options but dynamic for one option in particular, but I'd be more than happy with dynamic completions for all. (I gather it's all-or-nothing from the contents of register_minimal.bash.)

[epage]

Even static completion documentation is pretty bare bones (e.g. see #2488). Part of the problem is I don't setup completions for most applications and i only use bash, so I'm not in too much of a position to go through and document everything for every shell. I did at least update clap_complete on docs.rs to include the dynamic module (unsure why example scraping isn't working).

The expectation is that the static and dynamic completions are mutually exclusive. Once the dynamic completions are complete enough, we'll spin the static ones out and treat them even more as "community maintained" than they are today, making the dynamic ones the primary completion support we advertise.