OpenAPI: Replace legacy nullable fields with OpenAPI 3.1 null types - #17837
Open
yangshangqing95 wants to merge 1 commit into
Open
OpenAPI: Replace legacy nullable fields with OpenAPI 3.1 null types#17837yangshangqing95 wants to merge 1 commit into
yangshangqing95 wants to merge 1 commit into
Conversation
uros-b
approved these changes
Aug 28, 2026
Member
|
Seems like clean and complete OAS 3.0 -> 3.1 nullable migration |
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.
Description
Updates the REST Catalog OpenAPI schema to use OpenAPI 3.1 null types instead of the legacy
nullablekeyword.This ensures generated models correctly handle nullable values, including the required but nullable
snapshot-idfield. The generated Python models are updated accordingly.