I've been thinking about a good name.

... I found these discussions for the same feature request in a different CLI parser:

[Console] Explicitly passed options without value (or empty) should remain empty symfony/symfony#21228 -> This eventually got merged. Essentially same solution as picocli How to detect when String option was specified without value #279 .
[Console] Need way to determine if option was provided symfony/symfony#11661
[Console] Option with optional argument always returning null whether specified or not symfony/symfony#11572
[Console] Add method to know parsed option symfony/symfony#12773
[Console] Ability to use option default only if the option was passed symfony/symfony#12769 (comment)
[Console] Input options with InputOption::VALUE_OPTIONAL and InputOption::VALUE_NONE not working as expected symfony/symfony#8135 (comment)

Some possible names from that discussion: "tri-state option", "smart default", "optional argument for switches", "option without value"

Looking at your original description

the need for this is to allow the user to enable a feature and optionally to provide an extra parameter value.

Perhaps defaultSwitchValue is a good name that captures the essence that this is for "switch" options (where the presence or absence of the option itself is meaningful) as well as that this default value is separate from the "normal" defaultValue.

Customize value assigned when option specified without value #280

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions