What is next for the visualiser? Need your help!

[boyney123]

A couple of months ago we released the visualiser into the Studio, and from initial feedback, it seems that the community quite like it and find it valuable.

It would be good to understand what else we can do here to make it better?

If you have any ideas or thoughts please share them so we can explore and maybe start building them!

---

Ideas

1. Allowing the user to create AsyncAPI file from Visualiser (Drag, Drop Nodes and Connect them)

This idea came from @magicmatatjahu but the thought of allowing users to use this tool to build their AsyncAPI file, but using nodes and drag and drop interface.

Users will be able to create subscriber, publisher, and also application nodes and connect them together. When connecting them you will probably be prompted to enter various details about the node type you are connecting/adding.

---

I will add more ideas as time goes on

[jonaslagoni]

I am just shooting ideas out that is use-cases I could use, no filtration (some might be more for studio then visualizer) 😆

• I would love to see it support the visualization of multiple applications, i.e. you can see how applications interact with each other. Related to Support multiple applications #195. No idea how to separate such logic and what belongs where, if we compare it to Cupid 🤔
• Maybe the ability to inspect message payload structures and validation rules 🤔
• When the side menu is clicked, the message/operation gets highlighted or zoomed to.
• Quick action form to send example message to the application 🤔 I.e. a form of simulation (not mocking) of externals interacting with the application.
• When visualizing a single application, maybe show (shadowing) external applications that interact with it.
• Saving placements, i.e. if you restructure the placement of the boxes, it stays that way forever.

Love the creational aspect as you suggested!

[boyney123]

Thank you @jonaslagoni

Maybe the ability to inspect message payload structures and validation rules

Yeah great idea, at the moment I just added the messages as blocks onto the pub/sub boxes, but yeah the abilty to open them and inspect would be great. Thanks

When the side menu is clicked, the message/operation gets highlighted or zoomed to.

💯

Quick action form to send example message to the application

Nice. Do you mean the studio will know how to connect to the applications, and actually start sending real messages/logs etc?

When visualizing a single application, maybe show (shadowing) external applications that interact with it.

Yeah I like that, I guess it will be easier when we can support multi applications.

Saving placements, i.e. if you restructure the placement of the boxes, it stays that way forever.

Yeah shouldn't be too hard, guess we can just store them in local storage, thanks!

[magicmatatjahu]

@jonaslagoni I like your suggestions, but about multiple application we should have first some logic to handle multiple specs in the Studio like this one idea #167 and then use that feature inside Visualiser :)

[jonaslagoni]

Nice. Do you mean the studio will know how to connect to the applications, and actually start sending real messages/logs etc?

Yes!

With the AsyncAPI document, you should have all the information needed (in most cases at least, custom serialization and deserialization functionalities would be hard to support) to send single messages from the browser 🤔

[magicmatatjahu]

With the AsyncAPI document, you should have all the information needed (in most cases at least, custom serialization and deserialization functionalities would be hard to support) to send single messages from the browser 🤔

But also that should be as separate tool, not inside Visualiser, because someone should test app from raw AsyncAPI, not from Visualiser context, so that case it more related to Studio feature than Visualiser 😄

EDIT: You wrote about that it's related to Studio, not only to Visualiser, sorry 😅

[magicmatatjahu]

Related #265

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️