Generete reply information

[CodeGlitcher]

Reason/Context

Please try answering few of those questions

• Why we need this improvement?
  De asyncapi 3.0 spec allows for message reply to be defined. Generated documentation should reflect this.
• How will this change help?
• What is the motivation?
  Other team members can easily see how this api works and what data they should expect.

When operation specifies a reply.
I expect that the generated markdown include this.
I think the generator should add a reply header with the detail of the reply.

Description

Please try answering few of those questions

• What changes have to be introduced?

• Will this be a breaking change?
  Not sure

• How could it be implemented/designed?
  I think a Replay block with details should keep thing readable.

Reply

Reply table / details

Added my test input and current output:
current-output.md
input.yaml.txt

[github-actions]

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.

[korifey91]

I'm facing the same issue. In my spec file I have reply message and I need to see what message will be sent as a reply.

[derberg]

@CodeGlitcher please join review -> #523

[derberg]

solved with #523