How to disable deno linter for whole project directory?
I'm using deno with mixed project folders, some use Vue and shouldn't be linted by deno. How do i disable it for the project folder?
AIn
.vscode/settings.json
FI tried that, it did nothing
ANow I set
deno.lintsettings.json
A
AAnd I no longer have the deno lint warning.
Aie. It does seem to do something. Maybe try forcing the Deno LSP to restart using the command.
F
F
FI added it in
.vscode/settings.jsonRestarting deno lang server or vscode didn't help
FAlso upgraded vscode
FAlso reloaded window as someone suggested
AThat's not Deno's linting but the importing (ie. not a "don't do this, this may be bad code" but Deno itself saying "this will not work, it will throw an error in runtime"). Presumably you have the Deno language extension enabled globally, but in this case you only want to apply it selectively. Try adding the setting to control where you use the Deno LSP and where normal TypeScript LSP should be used.
Aeg. I just used to set only to be used by Deno. Now in my file I have this error:
FIt got disabled if i opened only that specific project folder
Fbut not in a workspace with multiple projects
A@frigjord And the reason why I say
Ah, then you might have it defined in the workspace settings.
Presumably you have the Deno language extension enabled globallyis due to not being in that settings.json.
Ah, then you might have it defined in the workspace settings.
A
FI disabled it globally, but still shows
AThen you might also have it turned on both globally and in the workspace settings 
AThere's "Open default settings (JSON)" and "Open user settings (JSON)" which can contain the same stuff.
AI just tested and indeed if you open the workspace settings JSON then it should (or can) contain a key which then can contain and . The paths is a bit annoying to use: It doesn't seem to understand "plain paths" eg. "dev/denostuff/libA" even though the folders definition for workspaces works this way. It also doesn't seem to understand relative paths from the workspace file. It does understand "plain paths" that it solves for each workspace folder individually, so eg. would work to enable Deno in both and .
It also works for absolute paths, so will works.
It also works for absolute paths, so will works.
A also comments that:
// When a value is set, the value of is ignored.So if you have an enable path that matches your current path, then even if you turn
deno.enable// Controls if the Deno Language Server is enabled. When enabled, the extension will disable the built-in VSCode JavaScript and TypeScript language services, and will use the Deno Language Server instead.
//
// If you want to enable only part of your workspace folder, consider using setting instead.
//
// Not recommended to be enabled globally.
"deno.enable": false,
FenablePaths is empty in both default and ws settings
AAnd
deno.enablefalseYes
AAnd did you check user settings as well?
A
AAlso just to check, what's your
deno --versionLatest deno, vscode settings.json has deno.lint false