-
### Describe the bug.
see the blank space between components and operations
whenever you expand and collapse a node in the tree the blank space is retained by the node even though it is not expand…
-
### Describe the bug.
The CLI tool now accepts asyncapi bundle for v3 documents (thanks to fix of issue https://github.com/asyncapi/cli/issues/1137). However, it does not work as I expected, but of c…
-
# Introduction
This proposal is to add a `version` field into the [message object](https://github.com/asyncapi/spec/blob/master/spec/asyncapi.md#message-object). This is to allow a more granular vers…
-
### Describe the bug.
As per spec v3.0.0 Operations are unique and only support a single Channel. Doesn't make much sense to return a `Channels` object since it should only contain only one `Channel`…
-
I have many big projects, with many endpoints. Some are webscockets, some are REST, and I can generate openapi / asyncapi documentation for them. Problemm is, when I change something (changed payload,…
-
### Describe the bug you found in AsyncAPI Docs.
it specifically says:
"It MUST contain a subset of the messages defined in the [channel referenced in this operation](https://www.asyncapi.com/docs/r…
-
So to rebuild this project with glee, the first step would be to convert the [openapi file](https://github.com/Souvikns/server-api/blob/master/openapi.yaml) to AsyncAPI.
We might have some issues …
-
**User Story**
As a partner team engineer, I want VRO to have a consistently defined and documented RabbitMQ request/response agreement strategy integrated into the codebase using tools like AsyncA…
-
**Describe the desired outcome from the user's perspective**
As an AsyncAPI consumer, I want to configure `zilla` to validate `http` responses consistent with an `AsyncAPI` specification.
**Accept…
-
# Roadmap
We know that some users are waiting for new broker support (like **SQS**/**MQTT**/etc.), but please be patient a bit longer.
Due to the inner project structure becoming much harder to …