Fix inconsistencies in value implementations #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are several inconsistencies between the implementations of methods in
DslParamsImpl
andRepeatingArgValues
For example, when calling
value()
on a normal parameter that is a list, it will throw an exception. Whereas, in a repeating group it will give the first value. Additionally, within a repeating group, it does not through an error if the parameter does not exist.Additionally,
hasValue
inDslParamsImpl
did not throw if the param did not exist, instead it returnedfalse
, which is different to what is stated in the java doc in the API