Custom schema format produces an error

[jonaslagoni]

Describe the bug

Custom schemaFormat gives the following error: T[String(...)] is not a function

Use the following AsyncAPI document:

asyncapi: '2.5.0'
info:
  title: Backend service API
  version: '1.0.0'
  description: |
    This is the website backend service that interact with users.
  license:
    name: Apache 2.0
    url: https://www.apache.org/licenses/LICENSE-2.0

servers:
  development:
    url: 0.0.0.0:1883
    protocol: mqtt
    description: Local development broker

channels:
  management/new/product:
    description: New order being placed
    publish:
      operationId: consumeNewProduct
      message:
        $ref: '#/components/messages/NewProductMessage'

components:
  messages:
    NewProductMessage:
      name: newProductMessage
      title: New product message
      summary: When a new product has been created.
      schemaFormat: application/schema+json;version=draft-2019-09
      payload:
        type: string

[JhoanAlvear]

can i help with this issue

[JhoanAlvear]

@jonaslagoni you need register custom schemaformt with method registerSchemaParser

[jonaslagoni]

@JhoanAlvear IMO the Studio should be able to understand AsyncAPI documents with custom schemas, that is not one of the supported ones, without giving an error 🙂

@magicmatatjahu any guidance you can add to solving it?

[magicmatatjahu]

@jonaslagoni @JhoanAlvear I understand that given error message is misunderstood, but we shouldn't change error's message based on JS error's message, so we should handle that problem in the parser-js side. We have PR for that asyncapi/parser-js#449. Also when we will merge it #434 we will see these errors:

So I think that we can close that issue, wdyt?

[jonaslagoni]

Up to you if you want to leave it or remove it, technically it's not solved, so I would probably say leave it 😄

[magicmatatjahu]

Fixed by #434 PR