Bug: Error supplying Required Value & Option with same Text

[Good-man]

@gsscoder

Given:

class Options
{
    [Value(0, Required = true)]
    public string Text { get; set; }

    [Option("option", Required = true)]
    public string Option { get; set; }
}

mycmd.exe "test" --option "test"

produces:

ERROR(S):
  A required value not bound to option name is missing.

  --option        Required.

  --help          Display this help screen.

  --version       Display version information.

  value pos. 0    Required.

whereas

mycmd.exe "test1" --option "test2"

works fine.

It's not apparent why passing the same value would cause commandline to behave differently.

[JeremyMorton]

This is especially common when you have integer options and values, since it can be common to want to specify 0 or 1 for both an option and a value.

[sajagi]

This bug is still present in the latest nuget package (2.1.1-beta), but it looks like it's fixed already in source code.