Auto Save Location

[ballcoach12]

I'm running the Studio editor from a Docker container. The browser screen just went all white on me and I assume this is due to an error in my YAML document. I need to recover my previous version that was auto-saved. Where is the YAML document auto-saved to?

Thanks

[magicmatatjahu]

Hello! Document is saved in the document item in the localstorage. If you can, would you paste that spec that is causing the errors? Studio should catch the errors in the spec and display them and not crash the application. Recently we had an update with support for 2.4.0 version so I am afraid that the new functionality may have a bug somewhere and I want to check it.

[magicmatatjahu]

Thanks! Really sorry for the problem! I found bug and already it's fixed - you can check it in the https://studio.asyncapi.com/ If you use Docker image, please fetch latest version :)

[ballcoach12]

Awesome! Thanks for the quick turnaround! I will pull the docker image.

[ballcoach12]

If you'd be willing, I would like to have a side discussion with you about how you guys went about building your editor and learn about the architectural choices that you made. My team is embarking on an initiative to build a language editor using Language Server Protocol, and we are considering whether to build from scratch or use a platform. If you'd be willing, I'd like to learn from your experiences building the AsyncAPI Studio.

[magicmatatjahu]

No problem :) As for the architecture, it will be changed in Studio (I don't have time to do it yet, but I would like to as soon as possible) and it's very simple, singletons for services/logic, UI is based on React. Studio is still in beta version and we are thinking how to make studio extensible through plugins (like plugins for visual studio code). As for our experience in writing Studio itself, it is not (big) as you would expect. It's a combination of all our tools that we create in AsyncAPI org + Monaco Editor (the same one that uses Visual Studio Code). When it comes to language service protocol, we use an official one for JSON and YAML (for VSC). For now we don't extend it with additional things related to AsyncAPI, but we have such plans :)

[ballcoach12]

OK. We are looking at Eclipse Theia as the platform for our editor. It's a pretty sophisticated platform (read: complex), but it has a beautiful extensibility mechanism; Visual Studio extensions magically run in it. Right now, we are weighing the cost/benefit of building our own platform or using Theia.