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
This change will impact both the JSONSchema type and the root document type (where a default dialect is allowed to be specified).
Note that OpenAPIKit will not (at this time) do anything with values of these fields other than store/encode/decode them. In the future we may indicate what values (i.e. what schema dialects) are supported by OpenAPIKit but for now we will not change the behavior of OpenAPIKit in response to the dialect specified.
Work on types in the OpenAPIKit (not OpenAPIKit30) module.
The text was updated successfully, but these errors were encountered:
Add support for specifying JSON Schema dialects at both document root and schema levels.
This allows OpenAPI documents to declare which JSON Schema dialect they use via the
keyword.
Add jsonSchemaDialect property to Document struct
Add schemaDialect property to JSONSchema.CoreContext
Add coding key for encoding/decoding
Resolvesmattpolzin#202
@ziad-ashraf7, sure. It’s not a rule that you must have an issue assigned, but I do suggest commenting on the issue in question just to mention you are poking at it and that way someone else doesn’t do the same work at the same time. You can choose to poke at an issue without even commenting though.
Uh oh!
There was an error while loading. Please reload this page.
See Specifying Schema Dialects in the new spec.
This change will impact both the
JSONSchema
type and the root document type (where a default dialect is allowed to be specified).Note that OpenAPIKit will not (at this time) do anything with values of these fields other than store/encode/decode them. In the future we may indicate what values (i.e. what schema dialects) are supported by OpenAPIKit but for now we will not change the behavior of OpenAPIKit in response to the dialect specified.
Work on types in the
OpenAPIKit
(notOpenAPIKit30
) module.The text was updated successfully, but these errors were encountered: