Primitive boolean reading a NULL ... (due to mismatch in models)

[rob-bygrave]

So there is an external issue which is a mismatch in models, effectively 1 model has a field mapped to Boolean and another has the same field mapped to boolean.

We have the JsonB model with the primitive boolean, reading json that has a value of NULL and this fails.

Conceptually this is an issue that should be solved as ... "fix the models so that they align".

An alternative view/question is ... should primitive boolean handling reading NULL? So it's null safe on reading but doesn't have to be null safe on writing?

I'm pondering this case, I don't know if JsonB should change by:

• Improving the parsing error reported for this case (it's ok'ish decent at the moment)
• Actually allowing null on reading primitive boolean (treat it as false, the default value)

[SentryMan]

if they want null instead of false they should use Boolean

[SentryMan]

I vote option 2

[rbygrave]

Note that Jackson ObjectMapper has DeserializationFeature.FAIL_ON_NULL_FOR_PRIMITIVES and by default allows nulls for primitives (so I'm thinking that avaje-jsonb mirrors this and allows nulls by default, has a configuration option for a "strict mode / failNullPrimitives=true" that then checks for nulls and throws a parsing error.

[SentryMan]

solved by #356