-
Notifications
You must be signed in to change notification settings - Fork 478
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
Option without value should throw an error. #861
Comments
I second this. There's no easy way of knowing whether a parameter was supplied without value or if it was omitted, and those are two different kinds of failure for us. |
Why would this throw an error? You have theres a third scenario:
Effectively 1 and 3 are the same |
https://github.com/commandlineparser/commandline/wiki/Option-Attribute
A string option should also force a value as with |
ull, enable the feature. This might seem backwards but it's not possible to pass ull to the options on the CLI, ull is just the absence of the option (or the absence of a value for the option, which is a different problem. see commandlineparser/commandline#861)
If I have a string option and it is called without a value, no error is thrown. This is what I would expect.
If i call this command line i get no error.
The text was updated successfully, but these errors were encountered: