-
-
Notifications
You must be signed in to change notification settings - Fork 125
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
[BUG] Messages aren't shown in sidebar unless they are used in operations #1106
Comments
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. |
hey there, so you would expect that if there are no operations, then messages get visible in sidebar, and if there are operations, they show up only as part of these? |
Hi @derberg, sorry for the delayed reply! As per the spec, I'd expect the messages/schemas to be visible in the sidebar regardless of whether or not they're used in operations. Looking at the reference implementation of the docs at https://studio.asyncapi.com/, this is indeed what happens when the operations/channels blocks are removed from the spec: |
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. |
Hey can you assign this issue to me and since I am a new contributor it would be great if you guys can guide me and help me resolve the issue |
Describe the bug.
For an AsyncAPI file that has no
operations
block, messages/schemas defined under thecomponents
block do not appear in the sidebar.Expected behavior
Even if messages are not used in operations, they should appear in the sidebar. This happens in the playground at https://studio.asyncapi.com/, for example. It is also specifically called out as a use-case in the docs here:
Screenshots
How to Reproduce
operations
block removed.asyncapi generate fromTemplate <asyncapi.yaml> @asyncapi/[email protected]
🥦 Browser
Google Chrome
👀 Have you checked for similar open issues?
🏢 Have you read the Contributing Guidelines?
Are you willing to work on this issue ?
Would like to help but I will need guidance as I'm not a front-end engineer 😅
The text was updated successfully, but these errors were encountered: