-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Closed
Labels
re-use: ref/id resolutionhow $ref, operationId, or anything else is resolvedhow $ref, operationId, or anything else is resolvedre-use: traits/mergesSelective or modified re-useSelective or modified re-usereview
Milestone
Description
It grieves me to even bring this up, as no one is a fan of the special-case behavior of $ref
with siblings in the Path Item Object. But I feel that it's extremely important to restore trust by making all valid 3.1 OADs also be valid 3.2 OADs. The change in PR #2657 would invalidate certain 3.1 OADs.
We did deprecate the special case in 3.1.1 with PR #2656, but we don't really have a published deprecation policy that would allow us to break compatibility.
I hesitate to suggest any sort of creative workaround here, as any exception to compatibility will just remind everyone of the 3.1 experience.
Metadata
Metadata
Assignees
Labels
re-use: ref/id resolutionhow $ref, operationId, or anything else is resolvedhow $ref, operationId, or anything else is resolvedre-use: traits/mergesSelective or modified re-useSelective or modified re-usereview