-
Notifications
You must be signed in to change notification settings - Fork 14
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
optional values not working #25
Comments
If I understand you correctly, then this behaviour is by design. I think @option(minimum=0, maximum=1) List getName(); boolean isName(); Which should give an optional argument that takes 0 or 1 values. You will On Wed, Nov 6, 2013 at 8:47 PM, fovea1959 [email protected] wrote:
|
that works. I thought the other seemed reasonable for a single value use case, but can work with it. Thanks. From: Tim Wood [email protected] If I understand you correctly, then this behaviour is by design. I think @option(minimum=0, maximum=1) List getName(); boolean isName(); Which should give an optional argument that takes 0 or 1 values. You will On Wed, Nov 6, 2013 at 8:47 PM, fovea1959 [email protected] wrote:
|
boolean isName() does not seem to work as expected: trying to make an optional switch that takes an optional value. Leaving the value off throws an ArgumentValidationException. See testOptionalPresentNoValue in this Junit test.
The text was updated successfully, but these errors were encountered: