fix: ensure that @Nullable does not incorrectly affect object schemas#5124
Open
Mattias-Sehlstedt wants to merge 2 commits intoswagger-api:masterfrom
Open
fix: ensure that @Nullable does not incorrectly affect object schemas#5124Mattias-Sehlstedt wants to merge 2 commits intoswagger-api:masterfrom
Mattias-Sehlstedt wants to merge 2 commits intoswagger-api:masterfrom
Conversation
Mattias-Sehlstedt
force-pushed
the
do-not-set-nullable-on-objects
branch
2 times, most recently
from
3043ce4 to
23de3a0
Compare
2 tasks
This was referenced Apr 23, 2026
Mattias-Sehlstedt
force-pushed
the
do-not-set-nullable-on-objects
branch
from
23de3a0 to
8f9aeb7
Compare
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.
Pull Request
Thank you for contributing to swagger-core!
Please fill out the following information to help us review your PR efficiently.
Description
Changes so that a
@Nullableannotation present on a model does not incorrectly settype: nullfor OAS 3.1 ornullable: truefor OAS 3.0. The nullable is instead dropped entirely. This since the resolving currently does not support an easy way of expressing nullable withrefs correctly as per:OAS3.0
{ "nullable": true, "allOf": [{ "$ref": "#/components/schemas/NestedObject" }] }or
OAS3.1
{ "oneOf": [{ "$ref": "#/components/schemas/NestedObject" }, { "type": "null" }] }Fixes: #5115
Type of Change
Checklist
Screenshots / Additional Context