-
-
Notifications
You must be signed in to change notification settings - Fork 627
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[📑 Docs]: expand documentation for the new traits merge mechanism introduced in v3 #1879
Comments
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). |
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 ❤️ |
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:
Code of Conduct
The text was updated successfully, but these errors were encountered: