Skip to content
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

Do not show reply address when empty #930

Open
charbonnierg opened this issue Mar 6, 2024 · 1 comment
Open

Do not show reply address when empty #930

charbonnierg opened this issue Mar 6, 2024 · 1 comment

Comments

@charbonnierg
Copy link

charbonnierg commented Mar 6, 2024

Description

I'm mainly using NATS as a message broker, which offers request/reply on dynamic addresses which are not indicated in the message payload or message header.

Thus, when documenting my applications with Async API, I use reply channels with empty address field.

However, the asyncapi-react component still displays:

Reply will be directed to the address specified at this location:

Alternatives

Maybe display a message like:

"Reply will be directed to an address according to client and server configurations"

This would be True with NATS, because client can choose the reply subject when sending a request, but I'm not sure it is more informational than simply removing the message.

Reasons

  • The current display is misleading, because there is no reply location at all, but the message still mention a reply location
  • The current display strongly looks like a checkbox and this can be disturbing for new users

Attachments

Here is the current output:

image

Here is the output on my fork:

image

Code changes can be found here

Copy link

github-actions bot commented Mar 6, 2024

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.
Keep in mind there are also other channels you can use to interact with AsyncAPI community. For more details check out this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant