Example definition for message object and message trait should be the same

[derberg]

Imho https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageObject.json#L73 should be replicated in https://github.com/asyncapi/spec-json-schemas/blob/next-major-spec/definitions/3.0.0/messageTrait.json#L70

cause if somebody will be allowed anything with examples in trait, then trait merging will never work

probably best solution would be to introduce separate reusable MessageExamples.json and reuse it in messageObject.json and messageTrait.json with $ref

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