attribute to identify function to call about spec HOT 5 CLOSED

No problem 😃

from spec.

Thanks for raising the issue @chris3081.

I guess the debate here is if we should standardize operationId. My bet is that we should do it in order to increase compatibility with OpenAPI 3. However, it's not that simple in AsyncAPI because there's no such thing as an "operation object". The publish/subscribe operations are, in fact, message objects. So adding operationId as an attribute of "message" would couple messages to operations, 1:1, and that's an architecture decision the spec should not be imposing.

That said, we can rework the spec in the next major version to have operation objects separate from messages. Something like the following:

publish:
  operationId: sayHello
  summary: Says hello.
  description: Publish a message to say hello.
  message:
   summary: A hello message
   payload:
     type: object
     properties:
       arga:
         type: string
       argb:
         type: string

This would be more similar to OpenAPI 3. But, just to make it clear, this should be done in a next major version as it's a breaking change. In the meantime, your solution looks good enough to bypass the limitation.

from spec.

@fmvilas are you sure the assignment is right? 😛

from spec.

Aren't you going to work on this? Sorry lad, fixing it now.

from spec.

🎉 This issue has been resolved in version 1.0.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

from spec.