Remove @JsonCreator annotation from Kotlin types#917
Merged
Conversation
…ion from Jackson 2.21+
sjohnr
approved these changes
Jan 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Jackson 2.21 introduced stricter detection for constructors and now flags the generated Kotlin 0-arg constructor as being annotated with
@JsonCreatorin addition to the constructor defined in the data class, leading to aConflicting property-based creatorsJsonMappingExceptionwhen the object mapper is used at runtime.This PR removes the
@JsonCreatorannotation entirely from generated Kotlin data classes.@JsonPropertyis kept for each field to maintain the mapping from JSON field to parameters. With this change, Jackson uses the explicitly defined non-0-arg constructor as the creator and avoids the conflicting creators exception.