Tatu Saloranta
Tatu Saloranta
In this case, I think I would actually suggest avoiding confusing/conflicting naming. So the original caveat may apply. If we can work around conflicts easily, great; but I don't want...
Value of `NON_DEFAULT` has been problematic for the longest time, unfortunately. I do not think there has been intentional changes, for what that is worth. But handling of Creators (and...
First things first: behavior of Jackson 3 is not really expected to be same as that of Jackson 2.x: a big reason for major version upgrade is the ability to...
Thank you for reporting this @MartinK99. At this point we'd probably need a contribution to fix it.
Missed 3.0, hope to tackle for 3.1
It seems like it should work. Could you try equivalent POJO case to see if that works?
Also: wrong repo, will transfer to correct one.
Ahh. I should have read this with thought: @JooHyukKim is right, content filtering only applies to POJOs and `Map`s -- basically name-indexed types. I suspect there might be another issue...
Probably 3.x-only idea, definitely starting there if anyone has the itch.
This is unfortanely a feature, not bug -- constructor in question is auto-detected as "Properties-based", expecting JSON Object, instead of "Delegating" that you would like. This is inherently ambiguous case....