You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2023. It is now read-only.
According to spec swagger inside schema object support only limited subset of JSON Schema draft4 and extend it with custom keywords.
Right now, you using "z-schema" validator which is work according to Draft4 spec.
So, you don't use "discriminator" and "readOnly" keywords during validation that mean you don't fully support Swagger 2.0 spec. At the same time your library successfully validate schemes which use such keywords.
Personally, I think it's a problem in Swagger spec.
So I created OAI/OpenAPI-Specification#333 feature request to make Swagger compatible with JSON Schema.
In other case we could have situation in which there is official spec but no one following it 😞
And I want library authors took part in that discussion.
The text was updated successfully, but these errors were encountered:
According to spec swagger inside schema object support only limited subset of JSON Schema draft4 and extend it with custom keywords.
Right now, you using "z-schema" validator which is work according to Draft4 spec.
So, you don't use "discriminator" and "readOnly" keywords during validation that mean you don't fully support Swagger 2.0 spec. At the same time your library successfully validate schemes which use such keywords.
Personally, I think it's a problem in Swagger spec.
So I created OAI/OpenAPI-Specification#333 feature request to make Swagger compatible with JSON Schema.
In other case we could have situation in which there is official spec but no one following it 😞
And I want library authors took part in that discussion.
The text was updated successfully, but these errors were encountered: