asyncapi/spec-json-schemas

Component messages can contain oneOf

jonaslagoni opened this issue · 3 comments

Describe the bug

According to the spec, a message in the component section should not be able to be defined with oneOf, but at the moment the following is valid:

components:
  messages:
    myMessage:
      oneOf:
        - name: LightMeasured
          payload:
            type: string

Expected behavior

Expected a validator to mark this as invalid input.

Is there more to do here?

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

Nope, lets close this 😄