Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
KathleenDollard opened this issue Apr 23, 2024 · 4 comments
Labels
Design Powderhouse Work to isolate parser and features

Comments

@KathleenDollard
Copy link
Contributor

No description provided.

@PonchoPowers
Copy link

Please retain, see #2433 for why it is required.

@jonsequitur
Copy link
Contributor

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

@baronfel
Copy link
Member

baronfel commented Jun 1, 2024

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
Copy link

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Design Powderhouse Work to isolate parser and features
Projects
None yet
Development

No branches or pull requests

4 participants