Improve handling of empty optional params #1332
Closed
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.
Fixes #1331.
Before this PR
When deserializing
OptionalInt
,OptionalLong
, orOptionalDouble
values used as header or query parameters, empty string values fail to deserialize withNumberFormatException
.After this PR
When deserializing
OptionalInt
,OptionalLong
, orOptionalDouble
values used as header or query parameters, empty string values deserialize as empty optional values.This is necessary to properly support optional header/query params for Conjure clients due to #790.
This also make the handling of primitive optional consistent with Jersey's handling of
Optional<T>
:https://github.com/jersey/jersey/blob/2.25.1/core-server/src/main/java/org/glassfish/jersey/server/internal/inject/ParamConverters.java#L81-L90
Possible downsides?
Optional<T>
. See Undertow endpoints cannot deserialize optional header params sent by Feign clients #1330.