Closed hauner closed 3 years ago
mapping a json payload to a java class looses the nullable information.
nullable
For example the following two payloads will produce the same java object for a model class with a single String property foo:
String
foo
{}
{foo: null}
Both will be deserialized to an object with foo = null. No way to know if it was missing or if it was null.
foo = null
This is a necessary info to implement PATCH with json merge patch:
PATCH
This could be implemented by using jackson-databind-nullable.
Because of the additional dependency it should be off by default and it gets enabled by setting a new configuration option.
mapping a json payload to a java class looses the
nullable
information.For example the following two payloads will produce the same java object for a model class with a single
String
propertyfoo
:{}
{foo: null}
Both will be deserialized to an object with
foo = null
. No way to know if it was missing or if it was null.This is a necessary info to implement
PATCH
with json merge patch:This could be implemented by using jackson-databind-nullable.
Because of the additional dependency it should be off by default and it gets enabled by setting a new configuration option.