Request/reply semantics not clear in generated html

[bjhartin]

Describe the bug

I can't get replies to appear the generated HTML files. Let me know if this is the wrong place.

Related: asyncapi/studio#919

How to Reproduce

• Paste this contract into a file 'asyncapi.yml' and run the cli's generate command with the html template.

asyncapi: 3.0.0
info:
  title: Test Contract
  version: 1.0.0
channels:
  PlaceOrder:
    address: 'Place Order'
    messages:
      PlaceOrder:
        $ref: '#/components/messages/NewOrder'
      OrderPlaced:
        $ref: '#/components/messages/OrderPlaced'
operations:
  PlaceOrder:
    action: receive
    channel: 
      $ref: '#/channels/PlaceOrder'
    messages:
      - $ref: '#/components/messages/NewOrder'
    reply:
      messages:
        - $ref: '#/components/messages/OrderPlaced'
      channel:
        $ref: '#/channels/PlaceOrder'
components:
  messages:
    NewOrder:
      payload:
        type: object
    OrderPlaced:
      payload:
        type: object

There is no indication that OrderPlaced is a reply that the publisher can listen for.

Expected behavior

I expected a client of my messaging API to be able to easily see request-reply semantics in the HTML interface (studio or the CLI).

[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.

[bjhartin]

Closing this because it was my misunderstanding.