[Design] Do we retain current `--` behavior (.NET CLI may be nonstandard)?

dotnet / command-line-api

Command line parsing, invocation, and rendering of terminal output.

https://github.com/dotnet/command-line-api/wiki

MIT License

3.34k stars 375 forks source link

[Design] Do we retain current `--` behavior (.NET CLI may be nonstandard)? #2399

Open KathleenDollard opened 2 months ago

PonchoPowers commented 1 month ago

Please retain, see https://github.com/dotnet/command-line-api/issues/2433 for why it is required.

jonsequitur commented 1 month ago

The System.CommandLine behavior (which matches POSIX expectations) is different from the .NET CLI behavior (which is nonstandard).

baronfel commented 1 month ago

I don't think we've raised an issue about the -- behavior of the .NET CLI yet - do either of you (@jonsequitur / @KathleenDollard) have a quick version I could use as the basis for one?

PonchoPowers commented 1 month ago

The System.CommandLine behavior (which matches POSIX expectations) is different from the .NET CLI behavior (which is nonstandard).

Surely then the standardised approach should be the one that is supported, which is how System.CommandLine behaves currently.

It might be wise to add a CliConfigurationOption to specify whether to use the standard, or non-standard version?