Enforce required nullable Kotlin/Jackson properties - #3333
Open
schani wants to merge 1 commit into
Open
Conversation
Generated-output differences55 files differ — 55 modified, 0 new, 0 deleted |
schani
force-pushed
the
fix/kotlin-jackson-strict-optional
branch
from
August 30, 2026 18:13
7f50017 to
e8816af
Compare
Generated-output differences55 files differ — 55 modified, 0 new, 0 deleted |
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
1 participant
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.
Required nullable constructor properties no longer get defaults. Jackson now marks them required while optional properties retain null defaults.\n\nEnables strict-optional schema tests.\n\nTests:\n- npm run build\n- focused strict-optional.schema\n- full schema-kotlin-jackson (85/85)\n\nOutput scope: five existing schema outputs change; other Kotlin frameworks retain current defaults.