Closed panesofglass closed 4 years ago
this also applies to normal switches, or nullary DUs - i.e. if you have BackColor, the switch will be --backcolor
, and --backColor
will be rejected. One workaround is to specify an [<AltCommandLine "backColor">]
. This however brings up a key point: AltCommandLine
, and in general switches for most commandline tools are not case-insensitive in general, so this would likely be problematic. Perhaps the help text display can emit a suggestion message i.e. "Did you mean --backcolor
?"
@bartelink I hadn't thought of that, but you are right. I'll close this. Thanks!
Description
Subcommands appear to be case sensitive.
Repro steps
Please provide the steps required to reproduce the problem
IArgParserTemplate
for a subcommand, e.g.type Test = Blah of ParseResults<OtherArgs>
test.exe Blah --otherargs
Expected behavior
Subcommand should be case insensitive.
Actual behavior
Usage is printed after
no valid subcommand has been specified.
Known workarounds
Pre-process arguments beforehand or ensure the correct casing is supplied in the command line args.
Related information