Allow disabling built in extensions

microsoft / vscode

Visual Studio Code

https://code.visualstudio.com

MIT License

164.22k stars 29.29k forks source link

Allow disabling built in extensions #17068

Closed dbaeumer closed 6 years ago

dbaeumer commented 7 years ago

VSCode Version: 1.8.0-insider

We have requests to support disabling all TS functionality. Instead of introducing a setting we should allow disabling built in extensions.

iammerrick commented 6 years ago

@nickshevr Free for all amigo https://code.visualstudio.com/insiders/

nickshevr commented 6 years ago

@iammerrick thanks a lot. Today is just my second day with VS Code after 2 years with WS, and you know, I almost like it.

nickshevr commented 6 years ago

@iammerrick I'm sorry for mention you agian, but I couldn't fix my issue. Is there any way to turn off TS checks but still use JS checks?

I want to fix this: But I dont want to turn off this:

iammerrick commented 6 years ago

  "javascript.validate.enable": false,
  "javascript.format.enable": false,

In your settings...

nickshevr commented 6 years ago

I tested it before Insiders build, don't like this way. As I said

I wanna still use JS checks (without ts features)

This method turns off all useful typed suggestions.

NP, I'll try another ways.

dsifford commented 6 years ago

@sandy081 This is great! Thanks so much.

I'm curious if there are any plans to add the ability to disable builtins from the command line?

I have a small script that I use to synchronize my installed extensions between machines that leverages the --list-extensions, --install-extension, and --uninstall-extension APIs and it would be awesome to be able to --disable-extension (with expanded support to @builtins) to synchronize the state of my disabled extensions.

Thanks again.

tafelito commented 6 years ago

Hi, I just installed the new vscode version 1.21.0 that allows you to disable builtin extensions. I disabled the TypeScript extension but I'm still having issues with the intellisense when using flow.

If I open a file from the explorer, and then from a different file I do "Go to definition" to the same file, that files opens twice.

If I remove // @flow then it doesn't do anything when trying to go to definition

Do I have to add any extra config?

Thanks

sandy081 commented 6 years ago

@dsifford Please open a feature request for your requirement

@tafelito Please open a new issue explaining the bug you are facing.

Thanks