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
The theme in monaco is, shockingly, a global variable, not a per-editor variable.
When a new <Editor> is created, it will set the theme. If no theme was explicitly set, it will set it to light. When you have multiple editors, this is wrong because spawning a new editor should not change the theme.
Instead, authors should be encouraged to set the theme themselves during beforeMount, with a hint that the theme is global.
The text was updated successfully, but these errors were encountered:
An alternative would be to not default to light: When no theme is passed (undefined), just don't call setTheme. I wouldn't do this because it still implies the wrong mindset about the 'theme' parameter being local, but it might be an easier sell because it won't break backward compatibility.
The theme in monaco is, shockingly, a global variable, not a per-editor variable.
When a new
<Editor>
is created, it will set the theme. If no theme was explicitly set, it will set it tolight
. When you have multiple editors, this is wrong because spawning a new editor should not change the theme.Instead, authors should be encouraged to set the theme themselves during
beforeMount
, with a hint that the theme is global.The text was updated successfully, but these errors were encountered: