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
Should these two separate typings be refactored to use only one of them across the core package? The openapi.ts typing does not include the unevaluated* keywords required for OAS 3.1.x /JSON Schema 2020-12 schemas.
I think this relates to #1546 where an unexpected keyword is throwing an error, but it is indeed valid for JSON Schema 2020-12 schemas to define any arbitrary properties.
In the previous version of OpenAPI 3.0.x, the schema object was strictly defined as a superset and subset of a JSON Schema draft-04 schema, and thus not all JSON Schema related behaviors applied. The interface design of OAS3_1Schema does not allow arbitrary properties.
The text was updated successfully, but these errors were encountered:
Good question. They are somewhat different as the first one is using for the code typing while the second one is for an OAS description typing. Ideally they should be synchronised, but I cannot come up with a reliable solution to enforce that.
redocly-cli/packages/core/src/typings/openapi.ts
Lines 160 to 164 in f11ebcb
redocly-cli/packages/core/src/types/oas3_1.ts
Lines 90 to 185 in f11ebcb
Should these two separate typings be refactored to use only one of them across the core package? The
openapi.ts
typing does not include theunevaluated*
keywords required for OAS 3.1.x /JSON Schema 2020-12 schemas.I think this relates to #1546 where an unexpected keyword is throwing an error, but it is indeed valid for JSON Schema 2020-12 schemas to define any arbitrary properties.
In the previous version of OpenAPI 3.0.x, the schema object was strictly defined as a superset and subset of a JSON Schema draft-04 schema, and thus not all JSON Schema related behaviors applied. The interface design of
OAS3_1Schema
does not allow arbitrary properties.The text was updated successfully, but these errors were encountered: