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

Connect reference context and target nodes #18

Open
handrews opened this issue May 22, 2023 · 0 comments
Open

Connect reference context and target nodes #18

handrews opened this issue May 22, 2023 · 0 comments

Comments

@handrews
Copy link
Member

  • For 3.0 Reference Objects, this means drawing the same edge that points from its parent to the Reference Object to the Reference Object's target
  • For Path Item Objects and 3.1 Reference Objects, there can be merging behavior (overwrite of summary or description for 3.1 ROs, no-conflict merging for PIOs), so in some sense unless the merge behavior is not used, there needs to be a new merge result node, and the original nodes (particularly in the PIO case) need to be indicated as not used directly
  • For Link Objects, operationRef and operationId behave more like a regular sub-object field that just happens to be done by reference. There probably just needs to be an operation edge that is present regardless of whether operationRef or operationId is used
  • For other direct (mapping in the Discriminator Object) and indirect (Security Schemes, Tags, ...) referencing, it's a little less clear what is needed, and might vary based on the exact reference type
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant