We currently use the CommandLineParser package to parse CLI options and arguments. However, it having an option that takes multiple values and multiple arguments at a time causes a parsing bug, because it does not follow the convention (--option foo bar baz instead of traditional --option foo --option bar --option baz).
On the other hand, the System.CommandLine package is backed by Microsoft and used by .NET Core's dotnet command. It seems de facto of the future for CLI parser, so I suggest we switch to this new package.
We currently use the CommandLineParser package to parse CLI options and arguments. However, it having an option that takes multiple values and multiple arguments at a time causes a parsing bug, because it does not follow the convention (
--option foo bar baz
instead of traditional--option foo --option bar --option baz
).On the other hand, the System.CommandLine package is backed by Microsoft and used by .NET Core's
dotnet
command. It seems de facto of the future for CLI parser, so I suggest we switch to this new package.