Set to true nullable bool arguments without the value

Consider the following class:

class Parameters
{
    [Option("bool")]
    public bool Bool { get; set; }
    
    [Option("nullable-bool")]
    public bool? NullableBool { get; set; }
}

It works fine for such arguments: --bool --nullable-bool true but doesn’t work for --bool --nullable-bool.

I suggest making it working for nullable bool types.

[mansellan]

Similar use-case. I want to allow --verbose or --quiet, but in my case, command line args are just one possible source for this (another is saved configuration). So I’d like it to be able to infer that for bool?, it will accept:

1. --{option} => true
2. --{option}=true|false => value
3. (omitted) => null

2 and 3 work just fine, but command-line users are used to using 1 for quickly switching things on, and I’d like to accomodate that.

[markdulfer]

I have a scenario where default settings are pulled from a database, but I want the ability to override certain settings with a commandline switch. In this case, I actually do want a nullable bool for flags. If the switch is not passed on the commandline (hence value = null) then use the default that came from the database, otherwise override with the commandline switch.