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

OpenApi 3.1 namespace - support assigning $schema in every Schema Object #362

Closed
char0n opened this issue Apr 14, 2021 · 1 comment · Fixed by #364
Closed

OpenApi 3.1 namespace - support assigning $schema in every Schema Object #362

char0n opened this issue Apr 14, 2021 · 1 comment · Fixed by #364
Assignees
Labels

Comments

@char0n
Copy link
Member

char0n commented Apr 14, 2021

$schema must be accessible from every Schema Object without traversing it's parents. We'll use meta of Schema Element to store this information there. This needs to be implemented on refractor level and no resolution should be done at this phase.

@char0n char0n added enhancement New feature or request OpenAPI 3.1 ApiDOM labels Apr 14, 2021
@char0n char0n self-assigned this Apr 14, 2021
char0n added a commit that referenced this issue Apr 16, 2021
This plugin transforms all Schema Elements in advance
and assigns information about inherited JSON Schema dialect to Schema Element.
One only has to inspect $schema property of Schema Element or
look into inherited meta property (inherited$schema) to determine
actual dialect of the Schema Element.

Closes #362
@char0n
Copy link
Member Author

char0n commented Apr 16, 2021

This functionality was finally implemented as refractor plugin as all other options proved to be significantly more complex.

char0n added a commit that referenced this issue Apr 16, 2021
This plugin transforms all Schema Elements in advance
and assigns information about inherited JSON Schema dialect to Schema Element.
One only has to inspect $schema property of Schema Element or
look into inherited meta property (inherited$schema) to determine
actual dialect of the Schema Element.

Closes #362
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant