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
I see this a fair amount as I switch between installs of stable and preview:
I'll NEVER EVER EVER want the ISE color scheme in VSCode. 😛
Rather than just switching the whole color scheme (even if just temporarily), what if the extension popped up a notification asking if the user wants to try the ISE (light) color scheme before switching (or even previewing) the color scheme. Or maybe add a setting to disable this?
What I don't know is if this something we do in the extension or if this is just a "feature" of VSCode when it detects a theme in an extension. Hmm, looks like this might just be a feature of VSCode.
The text was updated successfully, but these errors were encountered:
To expand, we've always bundled the theme, and one day VSCode changed behaviours to be more helpful, now this happens and the onus has been shifted to us to create a new deployment pipeline for a second extension just so that this doesn't happen.
Summary of the new feature
I see this a fair amount as I switch between installs of stable and preview:
I'll NEVER EVER EVER want the ISE color scheme in VSCode. 😛
Rather than just switching the whole color scheme (even if just temporarily), what if the extension popped up a notification asking if the user wants to try the ISE (light) color scheme before switching (or even previewing) the color scheme. Or maybe add a setting to disable this?
What I don't know is if this something we do in the extension or if this is just a "feature" of VSCode when it detects a theme in an extension. Hmm, looks like this might just be a feature of VSCode.
The text was updated successfully, but these errors were encountered: