AsyncAPI v3 shows warning in Studio and IntelliJ plugin when referencing a json schema

[ignacio-nyt]

Describe the bug.

AsyncAPI v3 shows warning in Studio and IntelliJ plugin when referencing a json schema file. The actual AsyncAPI document is rendered correctly but the warning in the editor persists.

Expected behavior

AsyncAPI v3 should be able to reference external json schema files without warnings.

Screenshots

How to Reproduce

1. I first created a valid JSON schema
2. I then created an AsyncAPI v3 doc referencing a JSON schema
3. Then I see the AsyncAPIv3 document rendering the JSON schema correctly but still showing warnings

Please rename the attached AsyncAPI v3 doc test.txt to test.yaml
test.txt
invoice_posted.schema.json

🥦 Browser

None

👀 Have you checked for similar open issues?

• I checked and didn't find similar issue

🏢 Have you read the Contributing Guidelines?

• I have read the Contributing Guidelines

Are you willing to work on this issue ?

None

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[jonaslagoni]

I think we have a problem with the JSON Schema files that describe payloads.

Payloads are defined with AnySchema:

spec-json-schemas/definitions/3.0.0/messageObject.json

Line 19 in 35ea790

"$ref": "http://asyncapi.com/definitions/3.0.0/anySchema.json"

AnySchema is defined with either schema or multiFormatSchema: https://github.com/asyncapi/spec-json-schemas/blob/master/definitions/3.0.0/anySchema.json#L8
Schema is basically just JSON Schema:

spec-json-schemas/definitions/3.0.0/schema.json

Line 5 in 35ea790

"$ref": "http://json-schema.org/draft-07/schema#"

For multiFormatSchema references should work if you dont define a schemaFormat:

spec-json-schemas/definitions/3.0.0/multiFormatSchema.json

Line 70 in 35ea790

"oneOf": [

For multiFormatSchema references should work for AsyncAPI Schema formats:

spec-json-schemas/definitions/3.0.0/multiFormatSchema.json

Line 122 in 35ea790

"oneOf": [

Same for all the other schema formats.

Looks like this is JUST a problem with AnySchema and Schema not adding reference type 🤔 Might be something to do with this:

spec-json-schemas/definitions/3.0.0/multiFormatSchema.json

Line 9 in 35ea790

"$ref": "http://asyncapi.com/definitions/3.0.0/schema.json"

[Pakisan]

@jonaslagoni yo, man, didn't see this thread

I digged into schema and found this - asyncapi/jasyncapi-idea-plugin#49 (comment)

Only schemeFormat = AsyncAPI or Schema broke validation

[Pakisan]

@jonaslagoni we must double check schemas generation

I found missing deadLetterQueue in SQS channel binding and fixed reference for queue

https://github.com/asyncapi/spec-json-schemas/blob/master/schemas/3.0.0-without-%24id.json#L5622

I created MR with example changes, which must me moved to generator + re-check bindings

I'm sure that more issues with validation will appear soon

[Pakisan]

@ignacio-nyt I have checked your specification and no more validation errors

wait for fix from our side

[ignacio-nyt]

@ignacio-nyt I have checked your specification and no more validation errors

wait for fix from our side

Thank you!