Use a common and managed Monaco Editor across the application#2380
Merged
rafaellehmkuhl merged 1 commit intobluerobotics:masterfrom Jan 28, 2026
Merged
Conversation
This update centralizes the Monaco Editor usage across the application, and makes it so the editor is initialized only once, and is reused globally. This prevents performance issues, like multiple instances being tracking data-lake variable changes at the same time, and also makes sure all usage have the same behavior.
c626b33 to
ea85f70
Compare
ArturoManzoli
approved these changes
Jan 28, 2026
Contributor
ArturoManzoli
left a comment
There was a problem hiding this comment.
Monaco is working fine after the migration
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This update centralizes the Monaco Editor usage across the application, and makes it so the editor is initialized only once, and is reused globally.
This prevents performance issues, like multiple instances being tracking data-lake variable changes at the same time, and also makes sure all usage have the same behavior.