You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
It's no secret that deno_lint is fast. Like, much, much faster than eslint. As such (and as the deno_lint roadmap heads toward eslint plugin compatibility and autofix), deno will see an increasing number of users and companies adopt deno lint for their linting solution, whether they use node, deno, or any other runtime.
Obviously, running lint in CI is nice, but most users want LSP integration, so that they can see lint issues as they write code.
Describe the solution you'd like
If this extension/lsp were to enable users to run the deno lsp purely for linting, without disabling normal typescript language features, and without enabling any other deno lsp features, we could have a hybrid world where users who use node, bun, etc, could use deno lint to great success.
This would increase adoption and awareness of deno tooling, and make other engineers happy.
Essentially, I wish the deno vscode extension would let us do "deno.enable": false, "deno.lint": true. In this sense, we get the linting features of the deno lsp without turning off visual studio code typescript language features.
Please consider this request! Let me know if I can provide any further information.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
It's no secret that deno_lint is fast. Like, much, much faster than eslint. As such (and as the deno_lint roadmap heads toward eslint plugin compatibility and autofix), deno will see an increasing number of users and companies adopt deno lint for their linting solution, whether they use node, deno, or any other runtime.
Obviously, running lint in CI is nice, but most users want LSP integration, so that they can see lint issues as they write code.
Describe the solution you'd like
If this extension/lsp were to enable users to run the deno lsp purely for linting, without disabling normal typescript language features, and without enabling any other deno lsp features, we could have a hybrid world where users who use node, bun, etc, could use deno lint to great success.
This would increase adoption and awareness of deno tooling, and make other engineers happy.
Essentially, I wish the deno vscode extension would let us do
"deno.enable": false, "deno.lint": true
. In this sense, we get the linting features of the deno lsp without turning off visual studio code typescript language features.Please consider this request! Let me know if I can provide any further information.
The text was updated successfully, but these errors were encountered: