You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Current (0.9.8) behavior is wrong: when processing split values, values exceeding max arity are pushed back onto the stack and are likely interpreted as positional parameters.
Instead, a MaxElementsExceededException should be thrown when the arity of a List or Map option has an upper bound, and the user specifies more values than the max.
The text was updated successfully, but these errors were encountered:
remkop
changed the title
WARN when multi-valued option max arity exceeded
Should throw UnmatchedParamEx when multi-valued option max arity exceeded
Aug 19, 2017
remkop
changed the title
Should throw UnmatchedParamEx when multi-valued option max arity exceeded
Should throw MaxElementsExceededException when multi-valued option max arity exceeded
Aug 19, 2017
Current (0.9.8) behavior is wrong: when processing split values, values exceeding max arity are pushed back onto the stack and are likely interpreted as positional parameters.
Instead, a
MaxElementsExceededException
should be thrown when the arity of a List or Map option has an upper bound, and the user specifies more values than the max.The text was updated successfully, but these errors were encountered: