v3.3: restore "propertyName" as required in the discriminator object#5228
Merged
ralfhandl merged 1 commit intoOAI:v3.3-devfrom Feb 27, 2026
Merged
Conversation
Erroneously removed in PR#4966.
ralfhandl
approved these changes
Feb 27, 2026
karenetheridge
changed the title
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
3 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.
propertyNameis now an optional field in the discriminator object: "The discriminator propertyName can now be an optional field." (https://github.com/OAI/OpenAPI-Specification/releases/tag/3.2.0)requiredkeyword was removed in the 3.2.0 validation schema (PR updates for the "xml" and "example" keywords #4966, yes that was me)propertyNameas required (https://spec.openapis.org/oas/latest#fixed-fields-21)Which results in the question: How is the mapping supposed to work without knowing what property name is to be used as the discriminating property?
When working through the examples I think the error is in the schema change (mea culpa), and the spec itself is correct.