fix: Kotlin nullability interpretation of Any? type - #3339
Merged
Merged
Conversation
bnasslahsen
added a commit
that referenced
this pull request
Sep 6, 2026
…of app25 The Kotlin Any? fix from PR #3339 stops markNullable from narrowing a schema that carries no type constraint. For a nullable $ref property the wrapper already expresses nullability through oneOf, so the extra type: "null" sibling (which made the property only ever validate against null) is now gone. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
bnasslahsen
pushed a commit
that referenced
this pull request
Sep 6, 2026
A schema representing Any? carries no type constraint, so it already permits any value including null. Leave it untouched instead of narrowing it to type: "null" (3.1) or decorating it with a redundant nullable: true (3.0). Backport of PR #3339 from the main line. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Fixes #3338