Tatu Saloranta comments

Results 3333 comments of


                                            Tatu Saloranta

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

Due to all complexities and ambiguity involved, so-called "delegating" constructors are not auto-detected (your Record-taking Constructor is delegating one; as opposed to Properties-based one). You do need to use annotation,...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

Ok, so: Jackson allows for at most: 1. One properties-based constructor (and if none annotated, no-args taking one essentially works as on) 2. One (full) annotated delegation-based constructor One challenge...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

@jessebarnum Almost -- but you are missing a setter or auto-detected field for delegating case? Basically something that does same as this: ``` @JsonCreator( mode = JsonCreator.Mode.PROPERTIES) public JacksonMultipleConstructorsExample( Triple...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

@jessebarnum Ok. I got confused with the example. This seems odd: ``` { "triple": { "a": 1, "b": 2, "c": 3 }, "d": 4, "e": 5 } ``` because structurally...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

> Seems like I put a start to this one. [#5084 (comment)](https://github.com/FasterXML/jackson-databind/issues/5084#issuecomment-2798918716). > > Shall we come up with draft solution in databind module as well, so we wont have...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

@jessebarnum Ok I just do not understand intent then. But one thing I did miss and should again warn -- part of FAQ. For test cases, PLEASE do not disable...

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

Ok, so: I think it'd be reasonable to change "mode" auto-detection/heuristics to consider single-Record-arg Constructor be considered delegating, a la: (assuming that wasn't working yet) ``` class Wrapper { @JsonCreator...

Tatu Saloranta

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

For multiple constructors, treat a single-arg record constructor as if it were a multiple-arg constructor with @JsonProperty annotations

Deserialization fails with version after 2.17.3 when DTO doesn't have no-args constructor

Deserialization fails with version after 2.17.3 when DTO doesn't have no-args constructor

@JsonUnwrapped and JsonTypeInfo.As.EXTERNAL_PROPERTY in the same bean doesn't work