spec-json-schemas
spec-json-schemas copied to clipboard
AsyncAPI schema versions
You can use an external JSON Schema validator in order to see if those files are valid or not. I've test it, and both seem invalid. - `2.0.0-rc1.json`: https://www.jsonschemavalidator.net/s/r114nPn0 -...
There is no rule written in stone, but as far as I have seen, we always advocated for requiring new maintainers of this repo to also be maintainers of the...
### Why do we need this improvement? It's important for our users, who are working with latest versions of Avro and OpenAPI specifications - OpenAPI: - 3.0.1 - 3.0.2 -...
#### Describe the bug Investigating some schema validation errors given at https://github.com/asyncapi/spec-json-schemas/pull/452, I found out that most of the properties from the `schema` definition in `2.0.0-rc1-without-$id.json` are pointing to `#/definitions/json-schema-draft-07-schema`....
**Description** After having a look at the `multiFormatSchema` file for https://github.com/asyncapi/spec-json-schemas/pull/495, there is no reason to do this extra check as everything comes through `anySchema`. Blocked by https://github.com/asyncapi/spec-json-schemas/pull/495
#### Reason/Context Following Go module major version suffixes creates complexity when releasing but also requires dependant libraries to manually update their `go.mod` and code in order to update to last...
### Describe the bug you found in AsyncAPI Docs. There are broken links in the [sns](https://github.com/asyncapi/spec-json-schemas/blob/master/bindings/sns/0.1.0/operation.json#L27) and [sqs](https://github.com/asyncapi/spec-json-schemas/blob/master/bindings/sqs/0.2.0/operation.json#L99) binding schemas. You can see some of the broken links below: -...
#### Describe the bug I get `Property name is not allowed.yaml-schema: AsyncAPI 3.0.0 schema.(0)` when using `name` parameter in `Security Scheme Object` in v3 spec. ![Screenshot 2023-11-08 at 4 04...
Imho https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageObject.json#L73 should be replicated in https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageTrait.json#L70 cause if somebody will be allowed anything with examples in trait, then trait merging will never work probably best solution would be to...
most of the context is in: https://github.com/asyncapi/spec-json-schemas/pull/421#discussion_r1410540517 now we have ```js module.exports = { 'schemas': { '2.0.0': require('./schemas/2.0.0.json'), '2.1.0': require('./schemas/2.1.0.json'), '2.2.0': require('./schemas/2.2.0.json'), '2.3.0': require('./schemas/2.3.0.json'), '2.4.0': require('./schemas/2.4.0.json'), '2.5.0': require('./schemas/2.5.0.json'), '2.6.0': require('./schemas/2.6.0.json'),...