[📑 Docs]: expand documentation for the new traits merge mechanism introduced in v3

[smoya]

What Dev Docs changes are you proposing?

@Fannon made a good point regarding the lack of expanded documentation regarding how the new traits merge mechanism works in v3.

Literally, the following is their comment:

Imho, it would be very nice to point to a reference implementation or code snippet how this is to be implemented correctly. As a Dev, I would feel more confident looking at a code example to check my understanding. I like the example, but a simple example cannot cover all the interesting corner cases :)

Originally posted by @Fannon in asyncapi/spec#907 (comment)

Code of Conduct

• I agree to follow this project's Code of Conduct

[Fannon]

Thanks for keeping track of this :)

I wonder if you could just point to an implementation, e.g. in an AsyncAPI documentation generator / renderer / playground. If you decouple the merge logic to its own function, it's easy to read and to write tests against it. (Maybe also link to tests? Some specs even provide test-suites specifically to test whether you implemented something correctly).

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