Inconsistency between Message.examples and MessageTrait.examples

[char0n]

Message.examples description

An array of key/value pairs where keys MUST be either headers and/or payload. Values MUST contain examples that validate against the headers or payload fields, respectively. Example MAY also have the name and summary additional keys to provide respectively a machine-friendly name and a short summary of what the example is about.

Message.trait description

An array with examples of valid message objects.

I propose we unify these description and use Message.examples description in Message.trait description.

If agreed I can issue a PR.

[magicmatatjahu]

@char0n Good catch! Message Traits examples should have this same shape as Message.examples. PR will be more than welcome :)

[char0n]

PR issued #608

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

[char0n]

PR #608 has been accepted and merged and became part of 2.2.0.