[modular] User-driven values (defaults, env vars, implied values, etc) #4793
Labels
A-parsing
Area: Parser's logic and needs it changed somehow.
C-enhancement
Category: Raise on the bar on expectations
S-waiting-on-design
Status: Waiting on user-facing design to be resolved before implementing
With clap today, each value source needs to be hard coded, including
default_value
default_missing_value
default_value_if
env
When new use cases arise, users either have to
It would help if clap had an API for users to provide their own systems for this. See also #3476.
Example unsupported use cases
default_value
anddefault_missing_value
are integral toAction
s, so I'm thinking we leave those as built-inRequirements
ValueSource
precedenceAction
behaviorTools
impl
of a trait for functionsInto
to allow custom plugin data to be converted to the plugin typeThe text was updated successfully, but these errors were encountered: