Declarative syntax for System.CommandLine via attributes for easy, fast, strongly-typed (no reflection) usage. Includes a source generator which automagically converts your classes to CLI commands and properties to CLI options or CLI arguments.
In version 1.5 nullable string properties give a warning:
[CliOption(Description = "Description for Extra")]
public string? Extra { get; set; }
Warning DMCLI33 DotMake.CommandLine.SourceGeneration -> The property 'Extra' has custom type 'string?' (other than supported CLR types) so it should have a public constructor or a static 'Parse' method with a string parameter, so that it can be bound/parsed as a CLI option .
I guess string? can be parsed automatically just like string
Well, I rushed the release, seems missed a check with nullable but that warning should not be harmful (if you can run and the option is parsed correctly). I will fix it shortly.
In version 1.5 nullable string properties give a warning:
Warning DMCLI33 DotMake.CommandLine.SourceGeneration -> The property 'Extra' has custom type 'string?' (other than supported CLR types) so it should have a public constructor or a static 'Parse' method with a string parameter, so that it can be bound/parsed as a CLI option .
I guess
string?
can be parsed automatically just likestring