Skip to content

v3.2: restore "propertyName" as required in the discriminator object#5227

Merged
miqui merged 1 commit intoOAI:v3.2-devfrom
karenetheridge:ether/3.2-propertyName-still-required
Feb 27, 2026
Merged

v3.2: restore "propertyName" as required in the discriminator object#5227
miqui merged 1 commit intoOAI:v3.2-devfrom
karenetheridge:ether/3.2-propertyName-still-required

Conversation

@karenetheridge
Copy link
Member

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.

  • schema changes are included in this pull request

@karenetheridge karenetheridge requested review from a team as code owners February 26, 2026 20:10
@ralfhandl ralfhandl requested review from a team and Copilot and removed request for a team and Copilot February 27, 2026 08:32
@miqui miqui merged commit 924a746 into OAI:v3.2-dev Feb 27, 2026
6 checks passed
@karenetheridge karenetheridge changed the title restore "propertyName" as required in the discriminator object v3.2: restore "propertyName" as required in the discriminator object Feb 27, 2026
@karenetheridge karenetheridge deleted the ether/3.2-propertyName-still-required branch February 27, 2026 18:08
karenetheridge added a commit to karenetheridge/OpenAPI-Modern that referenced this pull request Mar 1, 2026
...when the propertyName is not present in the data payload

This keyword is new in 3.2.0, allowing the property named by the propertyName
keyword (still required!) to be absent in the payload

see also OAI/OpenAPI-Specification#5227
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants