OpenAPI 3.1.0 support: useCircularStructures #2761
Assignees
Comments
char0n
added a commit
that referenced
this issue
Jan 10, 2023
char0n
added a commit
that referenced
this issue
Jan 11, 2023
char0n
added a commit
that referenced
this issue
Jan 16, 2023
char0n
added a commit
that referenced
this issue
Jan 17, 2023
char0n
added a commit
that referenced
this issue
Jan 18, 2023
char0n
added a commit
that referenced
this issue
Jan 23, 2023
|
🎉 This issue has been resolved in version 3.19.0-alpha.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
char0n
added a commit
that referenced
this issue
Jan 23, 2023
|
🎉 This issue has been resolved in version 3.19.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This issue has been resolved in version 3.19.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current implementation of
useCircularStructuresresolve option assumes that everything is JSON Pointer and construct absolute one when generating meta patches. Starting from OpenAPI 3.1.0 this is no longer true, as different mechanism can be used along with JSON Pointer, included but not limited to JSON Schema anchor, JSON Schema $id...useCircularStructuremust generate non-canonical JSON Pointer relative to current document.Schema URIs MUST be resolved against all parents before constructing absolute URI.
Circular structures MUST be handled for other types of elements as well.
Test with
useCircularStructures=truemust be provided for resolver.The text was updated successfully, but these errors were encountered: