dotnet / dotnet/command-line-api
Library has odd behavior if a user defined version flag is specified
Open
enhancement
- Dominant language
- C#
- Stars
- 3.7k
- Forks
- 428
- PR merge metrics
- No merged PRs in 30d
Description
Was converting an old app that had a --version flag to System.CommandLine. It seems that there's also a --version flag integrated into System.CommandLine, which was taking precedence. System.CommandLine should error if one of the specified root options interferes with one of the built in options.
Contributor guide
Assessment
This issue has not been assessed yet.