[BUG] Any non supported schema format should not make the doc invalid

[smoya]

Describe the bug.

Current supported schema formats are available in https://www.asyncapi.com/docs/reference/specification/v3.0.0#multiFormatSchemaObject.

If we try to parse a document containing an schema with, for example, schemaFormat: "application/octet-stream", the parser gives a validation error: Unknown schema format.

E.g.

Error thrown during AsyncAPI document parsing. Name: Error, message: Unknown schema format, stack: Error: Unknown schema format\n'

However, we find the following statement in the spec (same link as above):

Custom values are allowed but their implementation is OPTIONAL.

Expected behavior

Even though no custom schema parser is found for a given schema format, the document should still be valid as long as it is a string

Screenshots

How to Reproduce

import { Parser } from "@asyncapi/parser";
const parser = new Parser();
const { document, diagnostics } = await parser.parse(`
asyncapi: 3.0.0
info:
  title: Test custom schema format
  version: 0.1.0
components:
  schemas:
    theSchema:
      schemaFormat: application/octet-stream # This is allowed by the spec
      schema: true
`);

if (document) {
  console.log(document.info().title());
} else {
  console.log(diagnostics);
}

🥦 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

[AkshatJain481]

I would like to work on this issue

[yadavshubham01]

Hey @smoya, I have analyzed the issue and would love to contribute. Could you please assign it to me?

[MadhavDhatrak]

Root Cause

The current implementation in the parser throws an error when it encounters an unknown schema format

Proposed Solution

Modify the parser to accept custom schema formats while still validating that the format is a string:

This solution would fix the error in your screenshot because:
When it encounters application/octet-stream

• It won't throw the "Unknown schema format" error
• It will accept the format as valid since it's a string
• It will pass through the schema without modification

@smoya I would like to create a PR for this.