Option to override globally disabled extension in workspace settings

[ivancuric]

VScode currently has the option to disable an extension for certain workspaces.
However, there are extensions such as Arduino and the likes which are very workspace specific and negatively impact the overall experience if enabled outside that environment.

Instead of having to manually disable those extensions for every workspace, I suggest making it possible to enable an extension for a workspace even if it is globally disabled.

The current behaviour does not allow you to enable the extension for a workspace if it is disabled globally:

[dtasev]

👍 This could potentially speed up startup of vscode, by not starting all extensions by default (I am not sure how to time if it actually would make a significant difference).

Usage wise, I currently find myself to be disabling extensions depending on which are not used in the workspace. It would be nice to disable any language extensions globally, and only enable them if they're used in the current workspace.

[unional]

Duplicate of #15611

[vscodebot]

This issue has been closed because it is already tracked by another issue. See also our GitHub issues to search for existing issues and our issue reporting guidelines.

Happy Coding!