[regression] deno enable/disable command palette entries removed

There is no longer a VS Code command palette option to “Enable Deno” or to “Disable Deno” (it seems I must manually create the workspace settings file in every new workspace).

Screenshots

Versions

vscode: 1.48.2 deno: 1.3.2 extension: 2.0.16

[jsejcksn]

can you also share your use case of the enable/disable in command palette

@calvinlauco The Deno extension is disabled by default. I agree that it should be disabled by default because of conflicts with all non-Deno environments.

For every new VS Code workspace which will use the extension, it must be enabled. These are the steps to manually enable the extension in a new workspace:

1. Create a directory in the workspace root named .vscode.
2. Create a file in the .vscode directory named settings.json.
3. Add these contents to the file created in step 2:

{
  "deno.enable": true
}

If you only use a few workspaces, it is not a big deal to do that, but if you are frequently working in new Deno workspaces, it is not a scalable solution, and it’s much simpler to use the command palette like this:

1. <kbd>shift</kbd> + <kbd>ctrl/cmd</kbd> + <kbd>p</kbd>
2. <kbd>d</kbd><kbd>e</kbd><kbd>n</kbd><kbd>o</kbd><kbd> </kbd><kbd>e</kbd><kbd>n</kbd><kbd>Enter</kbd>

The same is true for disabling it in a workspace where it is enabled.

That is why I have labeled this issue as a regression—it removed an accessibility feature that’s never in the way, but it’s a huge help to anyone who used it.

[lucacasonato]

We have Deno: Initalize Workspace Configuration command in version 3.x. We won’t implement separate enable and disable commands.