Deno appears in the status bar regardless of whether workspace has "deno.enable": true

I don’t see any code that prevents this as right now the commands are registered and then it runs the code to start the language server.

We should register the commands, but only start the language server when the extension is enabled. If someone runs the “Deno: Restart Language Server” command and "deno.enable" is not true, then we should tell them to run “Deno: Initialize Workspace”.

I checked my global configuration and "deno.enable" was not true.

[kitsonk]

Yeah, the challenge is that there is no great way to “detect” a Deno project. It would be guessing. We are working on a optional unified meta data file, and that would allow us to “magically” enable Deno for a project without having to do it explicitly.

[dsherret]

@lucacasonato I just find it weird that I’m working on something unrelated to Deno, don’t have formatting enabled to use Deno, and don’t have "deno.enable": true in the repo and yet I see it running in the bottom right corner. I’d rather it not start at all in this scenario. Thinking about it more, I guess yeah if someone is using it for formatting then it’s less maintainable to have two ways of doing something. I think in that case to simplify things then we should start it, but not in my case here where it has no use.