Fix handling of vararg deserialization #743
Merged
+128
−5
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.
Previously, if the input was
undefined
for avararg
argument, it was treated as ifnull
had been entered.This is the same behavior as with
databind
.On the other hand, in
Kotlin
, thevararg
argument is alwaysnon-null
, which causes an error.Therefore,
vararg
arguments are now treated as if they were arguments with an empty array as the default value.This allows deserialization even if the input to the
vararg
argument isundefined
.In addition,
vararg
arguments are now basically treated asnon-required
.from: ProjectMapK/jackson-module-kogera#197