[3.0.0] Incorrect introduction to AsyncAPI

[jonaslagoni]

Describe the issue

In the current version 3.0 of the spec the first introduction of what an AsyncAPI file describes:

The file(s) MUST describe the operations an application accepts. For instance, consider the following AsyncAPI definition snippet:

user/signedup:
  subscribe:
    message:
      $ref: "#/components/messages/userSignUp"

It means that the application allows consumers to subscribe to the user/signedup channel to receive userSignUp messages produced by the application.

Is no longer valid with the switch of operation keywords from #806

[asyncapi-bot]

🎉 This issue has been resolved in version 3.0.0-next-major-spec.8 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

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 ❤️

[jonaslagoni]

Already solved