Tatu Saloranta

What @ragnese said, with just one twist: `DELEGATING` means that the incoming JSON value must match the argument value, and nothing else -- typically used with simple scalar types like...

One comment on test: please avoid "write then read immediately" construct on reproductions; or, if using both, verify both intermediate JSON and resulting object. This way it is possible to...

Unfortunately definition of `NON_DEFAULT` is complicated, and specifically is different between global default and per-class annotation-based variant. I am thinking that this is the same issue as: https://github.com/FasterXML/jackson-databind/issues/1757 Ultimately, if...

@Quantum64 yes, I understand usefulness: my only concern really is the correctness and reliability -- compared to simpler criteria like "no nulls" or "no nulls or empty Objects/Arrays", the current...

I think it is? Some options for setting defaults have been removed (methods in `ObjectMapper`), but I don't think I have removed that as setting (nor have concrete plans to...

@slu-it I suspect this is due to 1-argument constructors being ambiguous by nature: they can either be "delegating" (in which the whole incoming JSON value must directly map to type...

Ah. Looking at your example it is rather.... complicated. The issue is that you actually want to use TWO levels of constructors, so BOTH delegating AND properties, at different levels....

(transferred since this appears to be Kotlin-related, wrt naming)

@fire-papaya Can this be reproduced with plain Java? If not, I'll move this to Kotlin module; XML module has no knowledge of Kotlin handling. If reproducible with just Java, can...

One quick comment: change would definitely need to be against 2.13 branch, to minimize risk of breakage (which I think there is just due to scope).