Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolving implicit connections (3.0.4 port of #3856) #3906

Merged
merged 10 commits into from
Jun 17, 2024

Conversation

handrews
Copy link
Member

@handrews handrews commented Jun 13, 2024

Since we chose the simpler of the two ways to handle this, we can just directly backport the guidance instead of needing to rework it for 3.0. 🎉

[EDIT: Except changing "URIs" to "URLs" in the relative resolution link, which I missed but have now added as a separate commit.]

handrews and others added 9 commits June 13, 2024 10:33
This clarifies how to handle resolving implicit (non-URI-based)
connections in multi-document OpenAPI Descriptions.

While the behavior is implementation-defined overall, this
RECOMMENDS a single approach based on how things behaved going
back to the 2.0 referencing model.  This allows Security Schemes
and Tags to (like the top-level Server Objects) define
a deployment-specific interface for referenced documents to access.

This entry document interface approach makes less sense for the
Discriminator Object, but it can use the URI syntax of `mapping`
to keep things within the local document.

This also aligns the search for matching `operationId`s with
3.1's full-document parsing requirements.

Note that the term "complete OpenAPI document" has been defined
in another change pending approval on the 3.0.4 branch.
Co-authored-by: Ralf Handl <[email protected]>
@handrews handrews added clarification requests to clarify, but not change, part of the spec re-use: ref/id resolution how $ref, operationId, or anything else is resolved approved pr port PRs that just port an approved PR to another version labels Jun 13, 2024
@handrews handrews added this to the v3.0.4 milestone Jun 13, 2024
@handrews handrews requested a review from a team June 13, 2024 19:13
Copy link
Contributor

@miqui miqui left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ralfhandl Looks good to me. Thoughts?

@ralfhandl ralfhandl merged commit 11fc80e into OAI:v3.0.4-dev Jun 17, 2024
1 check passed
@handrews handrews deleted the implicit-304 branch June 17, 2024 18:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved pr port PRs that just port an approved PR to another version clarification requests to clarify, but not change, part of the spec re-use: ref/id resolution how $ref, operationId, or anything else is resolved
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants