Message details (payload) not rendered correctly when $ref is used in channels

[AMulgrave]

asyncapi.yaml.txt

Loading the yaml attachment into VS Code renders as follows:

Note the missing payload details for the channels messages using $ref.

While the same yaml renders correctly in Web Studio beta:

The rendering is also incomplete when the channels messsages are $ref to external asyncapi yaml files.

[ivangsa]

Hi @AMulgrave

thanks for taking the time to report this

You are right, this asyncapi.yml file renders alright in https://studio.asyncapi.com/
but it fails to render in vscode.

I will need to investigate further.

[ivangsa]

Hi @AMulgrave

we have investigates this issue, and we a reporting it to the react-component upstream...

Any way, you can simplify your asyncapi.yml definition without loosing any readability or reusability, for instance placing the channels section as first child (instead of inside components) would solve this rendering problem... I'm not sure what advantage you see in that indirection from channels -> component/channels

[ashmit-coder]

HI @ivangsa ,
was working on the same issue and found the same cause.
Just wanted to ask if have you created a issue for it, If so could you please refrence it here.

In the case you haven't I would like to work towards it.

[ivangsa]

@ashmit-coder please, go ahead an create a PR!
Out of curiosity, if you can share the details of what it's about..

[ashmit-coder]

Out of curiosity, if you can share the details of what it's about..
sure i wiill i need to look into to the working of the asycapi-react project. i will share my findings as soon as possible

[AMulgrave]

Hi @AMulgrave

we have investigates this issue, and we a reporting it to the react-component upstream...

Any way, you can simplify your asyncapi.yml definition without loosing any readability or reusability, for instance placing the channels section as first child (instead of inside components) would solve this rendering problem... I'm not sure what advantage you see in that indirection from channels -> component/channels

This is just an example to show the issue from a single file. In my project the channel definitions are in an external file.

[ashmit-coder]

Hi @AMulgrave
we have investigates this issue, and we a reporting it to the react-component upstream...
Any way, you can simplify your asyncapi.yml definition without loosing any readability or reusability, for instance placing the channels section as first child (instead of inside components) would solve this rendering problem... I'm not sure what advantage you see in that indirection from channels -> component/channels

This is just an example to show the issue from a single file. In my project the channel definitions are in an external file.

Could you please provide aother image this one is not visible

[AMulgrave]

In practice, I have the yaml structured that way to provide links to external yaml definitions. For simplicity, I provided the example to show the issue in one yaml file.