You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the playground uses Ace as its editor UI. In general this seems to work well, but it requires us to maintain custom syntax highlighting code which can become out of sync with the current state of the language (as happened here).
If we were to instead use Microsoft's Monaco editor, we could reuse the language configuration defined in this vscode extension, which should be less likely to get out of sync.
The text was updated successfully, but these errors were encountered:
Does Monaco supports LSP? This would be a double-win, because we currently have a kind of proto-LSP built in WASM in order to show errors directly inside the editor. It's obviously much less featured, and yet something else to maintain.
Currently the playground uses Ace as its editor UI. In general this seems to work well, but it requires us to maintain custom syntax highlighting code which can become out of sync with the current state of the language (as happened here).
If we were to instead use Microsoft's Monaco editor, we could reuse the language configuration defined in this vscode extension, which should be less likely to get out of sync.
The text was updated successfully, but these errors were encountered: