Undefined behaviour of "messageId" for Message Traits and Messages defined in components.

[tomsfernandez]

HI! According to the specification from version 2.4 and onwards, the messageId field:

The id MUST be unique among all messages described in the API. The messageId value is case-sensitive

Now, what happens if I define a messageId in a trait or in a component? I will only be able to re-use that trait or component one time because if I reference it more than once then I would be repeating messageId. Is this the correct interpretation of this feature or should I be thinking it differently ?

How is tooling handling these cases?

[github-actions]

Welcome to AsyncAPI. Thanks a lot for reporting your first issue. Please check out our contributors guide and the instructions about a basic recommended setup useful for opening a pull request.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

[ScottSusman]

Same question.

[derberg]

Solved with 3.0

Prior, yes, you kinda have a problem that if you will put messageId in a message trait or operationId in an operation trait and then reuse those in multiple messages/operations in the same document you will get an issue as it basically means you duplicate the ID information - reason is that for traits JSON Merge Patch is used