Tatu Saloranta

`@JsonUnwrapped` does not work with Constructor-based deserialization. There is an earlier issue #1467 that covers it. @Taz03 If there was an update, it would be noted here. There isn't, hasn't...

Actually there might be way forward for this, see #4271.

Since #1467 fixed, this as well; closing.

Quick question: is this actually still a problem, as: https://repo1.maven.org/maven2/com/fasterxml/jackson/module/jackson-module-kotlin/2.10.0/ does have source jar? I have no objection to patch #175 (going over PRs now), but want to make sure...

So it seems (looking at 2.17.2 sources). Reopening.

Quick note: usually it's a Bad Idea to use this for any tests: @JsonIgnoreProperties(ignoreUnknown=true) since it tends to mask all kinds of problems. Aside from that, yeah, nested POJOs are...

Right; either this needs to move to `jackson-module-kotlin` (I can transfer if so), or reproduction should be in Java. But I think there is probably already an issue wrt `@JsonAnySetter`...

Wait, what is that `@JsonIgnore` doing here??! ``` @JsonIgnore @JsonAnySetter @JsonAnyGetter val additionProperties: Map? = null, ``` wouldn't that mean "ignore this any setter/getter"? That should not be added there.

@MaximValeev it is possible `@JsonIgnore` does no harm, but in general it is to remove accessor (getter, setter, field, ctor parameter) from consideration (or if no inclusion, whole property). And...

@k163377 Yes, I think it's matter of getting #562 resolved (via #4558) and then Kotlin side probably wants to have a test to verify things work there as expected. But...