Severin Kistler

Yes, @yawkat, this is would be my first idea that would use existing annotations. I could also imagine some other annotation or argument to `@JsonProperty` that allows arguments of type...

I *think* the `record` is not necessarily relevant here, but rather the constructor/JsonCreator (see below). At least, I still got the same error using these two final classes (IntelliJ ->...

About the use of the `Map`, I used it as it was the only solution I found to make deserialization work with records. Anyway, here is a simpler reproduction (I...

@yihtserns I suspect at this time we were using jackson within Spring Boot version ~ 2.7.0, so I suspect ~ jackson 2.13.3, as this version was bundled at this time.

Yes, @yihtserns, you are indeed correct. I want it to be *any* number, not just it's ordinal value. I know the functionality you suggested that would use the ordinal value....

Oh, this is new to me. I suppose I never fully read the JavaDoc of @JsonValue to find this behaviour (Probably because I simply would not have expected it). Thanks...

As far as I understand it now, using `@JsonProperty` can be considered a shortcut notation compared to using `@JsonValue` with a `String` field on the enum. In that case, I...

Thanks for the detailed answer, I appreciate it. I expected something along those lines to explain the observed behaviour. I suppose we can close this issue then?

I just discovered this plugin (it's great, thanks!) and immediately I missed these two methods being generated ffor inner class builders. Would be even better if the builder would not...

Upon implementing a PR to see if my proposed feature can be implemented without too many changes, I realized that my current workaround does not even work as I thought...