Ability to disable extensions #23941
Replies: 4 comments 8 replies
-
|
+1! I would also love the ability to disable some language servers per workspace. |
Beta Was this translation helpful? Give feedback.
This comment was marked as spam.
This comment was marked as spam.
-
|
While I appreciate the desire to be able to enable/disable extensions so that workspaces only have the extensions they need, I'm unclear of what the design of such an implementation would look like.
I'm opened to exploring ideas for how such a system might be designed. |
Beta Was this translation helpful? Give feedback.
-
|
Extensions can now register ts plugins. When the ts plugins registered by two extensions conflict, I need to disable one of the ts plugins. I think disabling the extension in the project configuration is a good solution. e.g: gem extension conflicts with vue extension
|
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
-
Check for existing issues
Describe the feature
Extensions should be allowed to be disabled via some setting, at both the global and local level, so workspaces can disable plugins they don't need running.
If applicable, add mockups / screenshots to help present your vision of the feature
No response
Beta Was this translation helpful? Give feedback.
All reactions