Repository navigation
feat: add JavaNullablePropertyCustomizer to handle nullable properties in OpenAPI schemas - #3382
Open
Mattias-Sehlstedt wants to merge 1 commit into
Open
Mattias-Sehlstedt wants to merge 1 commit into
Mattias-Sehlstedt wants to merge 1 commit into
Conversation
Mattias-Sehlstedt
force-pushed
the
java-nullable-customizer
branch
from
October 8, 2026 18:27
70e3698 to
4ed6e2c
Compare
…s in OpenAPI schemas
Mattias-Sehlstedt
force-pushed
the
java-nullable-customizer
branch
from
October 8, 2026 18:40
4ed6e2c to
1532763
Compare
Mattias-Sehlstedt
changed the title
This branch has not been deployed
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.
Implements the existing behavior from Kotlin with nullability (
KotlinNullablePropertyCustomizer) resolving for ref:s in Java.Note that this behavior is configurable, and that it is opt-in. So there should be no issues with consumers getting a surprise behavior that they cannot easily disable.
This feature also already considers a missing case for nullability that has been handled in #3381 for Kotlin.
The expectation is that this logic will later live in swagger-core, see for example swagger-api/swagger-core#5077 (comment). But until then it would be helpful to provide the behavior here.