Config file ignored when linting
See original GitHub issueIf you specify a config file in deno.config
and that config deno.json
file disables linting rules such as:
{ "lint" : { "rules" : { "exclude" : ["no-unused-vars"] } } }
VSCode Deno plugin still shows all lint errors. Seems to ignore the config file entirely when it comes to linting.
If I run deno lint --config ...
from the command line, it works fine, the lint error is ignored.
vscode: 1.60.2 deno: 1.15.1 extension: 3.9.1
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Ignoring Code - ESLint - Pluggable JavaScript Linter
You can tell ESLint to ignore specific files and directories using ignorePatterns in your config files. ignorePatterns patterns follow the same rules as...
Read more >Warning for ignored files on linting · Issue #9977 - GitHub
It seems like the answer to this problem has previously been to just run eslint on directories and to avoid lists of files...
Read more >Should linters config files be in .gitignore? - Stack Overflow
Things like editor config files belong only in the user's global git ignore. Otherwise, your project has to explicitly ignore config files for ......
Read more >Configuration — SQLFluff 1.4.5 documentation
SQLFluff uses nesting in its configuration files, with files closer overriding (or ... Types of errors that can be ignored include: lexing. linting....
Read more >Ignoring Code - Prettier
Use “prettier-ignore” comments to ignore parts of files. Ignoring Files: .prettierignore. To exclude files from formatting, create a .prettierignore file in the ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Weird, it turns out it’s a different extension I have that is using
vscode.languages.getDiagnostics()
to get the current errors and then display them inline. For whatever reason it’s still showing thedeno-ts
errors in there, even though they are ignored by the config file. I’ll have to troubleshoot that, see if I can determine if there is some sort of error cache somewhere that’s not being flushed. Thanks for the help, sorry to bother with a ‘Not a bug’ 😃In you example I only get this diagnostic:
which comes from the TypeScript’s server not the
deno lint