[Linter] Make `deno lint` work in VScode without deno server
See original GitHub issueIs your feature request related to a problem? Please describe.
I wanted to use deno linter instead of eslint in VSCode for the project that is not deno-specific. I run deno lint
on my project’s code and the issues it finds are very useful for me, but I hate fixing them from the console, and I would greatly appreciate to see them as… well… lint output in the VSCode. But it seems it does not work 😦
Is it possible to have this functionality in this extension?
My workspace config I tried to use:
{
"deno.enable": false, // As I don't want to use deno. Deno will not handle imports (standard imports; dependencies defined in package.json)
"deno.lint": true,
"eslint.enable": false
}
After restarting VSCode I don’t see any linting messages in VSCode. It looks like deno.enable: false
turns extension off.
And screenshot showing that indeed it’s not working:
Describe the solution you’d like
I would love to use deno lint in the VSCode without enabling deno support. It should be possible, because deno lint
works fine from the terminal.
And I would love to see these warning/errors marks directly in the code
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:5 (4 by maintainers)
Top GitHub Comments
Any way I can help move this along?
Thanks for opinions! That definitely sounds like a good idea.