-
Notifications
You must be signed in to change notification settings - Fork 418
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
Make "allow option overwriting" configurable #129
Labels
Milestone
Comments
Also "warn" if parameters values diverge may be a good idea.
…On Thu, May 25, 2017, 02:26 Remko Popma ***@***.***> wrote:
Currently picocli accepts multiple occurrences of options with arity=1 and
uses the last value.
It may be desirable to throw a SuperfluousParameterException instead.
@ddimtirov <https://github.com/ddimtirov> suggested making validation
behaviour configurable:
1. accept and silently use last value
2. accept and emit warning while using last value
3. reject (throw exception)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#129>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAV8wqeXoGXgMksxtETp0dz_HNUDros9ks5r9Gg9gaJpZM4NlbOY>
.
|
#138 has been implemented, with an option to switch the validation off (the last specified value is used in that case). What hasn't been done yet is providing an option to emit warnings |
Created #158 for the remaining work. Closing this ticket. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently picocli accepts multiple occurrences of options with arity=1 and uses the last value.
It may be desirable to throw a
SuperfluousParameterException
instead.@ddimtirov suggested making validation behaviour configurable:
The text was updated successfully, but these errors were encountered: