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

Link Object: require referencing operation with unambiguous path template #4084

Open
ralfhandl opened this issue Sep 11, 2024 · 0 comments
Open
Labels
bug re-use: ref/id resolution how $ref, operationId, or anything else is resolved
Milestone

Comments

@ralfhandl
Copy link
Contributor

Assume paths /foo and /bar both have a Path Item Object that $ref the same external "complete" Path Item Object.

If a Link Object now operationRefs the get Operation Object within that external Path Item Object, which request should the client construct?

It could be both

  • GET /foo or
  • GET /bar

Proposal:

  • Add restriction to Link Object that operationRef and operationId MUST NOT reference a reusable/multi-used Path Item Object
  • Possibly: require that the operationRef value "goes through" a Paths Object
@ralfhandl ralfhandl added the bug label Sep 11, 2024
@ralfhandl ralfhandl added this to the v3.2.0 milestone Sep 11, 2024
@handrews handrews added the re-use: ref/id resolution how $ref, operationId, or anything else is resolved label Sep 11, 2024
@handrews handrews modified the milestones: v3.2.0, v3.3.0 Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug re-use: ref/id resolution how $ref, operationId, or anything else is resolved
Projects
None yet
Development

No branches or pull requests

2 participants