fix: distinguish between default and example set to null and not set at all #2050#2286
Open
ewaostrowska wants to merge 2 commits intomasterfrom
Open
fix: distinguish between default and example set to null and not set at all #2050#2286ewaostrowska wants to merge 2 commits intomasterfrom
ewaostrowska wants to merge 2 commits intomasterfrom
Conversation
daniel-kmiecik
approved these changes
Mar 6, 2026
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.
This pull request improves how default values are handled when converting Swagger V2 specifications to OpenAPI V3, ensuring that defaults are only set in schemas when explicitly provided in the source and never set to
nullunintentionally. It also introduces comprehensive tests to verify correct null/default handling for parameters, properties, and examples.Enhances the logic introduced in #2171.