Add lint name in "Problems" panel
See original GitHub issueWhen displaying a lint in the “Problems” panel it would be helpful to show the name of the lint. This would make ignoring the lint with the // ignore:
comment easier.
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
How To Lint and Format Code with ESLint in Visual Studio Code
ESLint is a linter that you can integrate into your Visual Studio ... The key will match the name of the rule you...
Read more >Linting Python in Visual Studio Code
Enable linting To enable linters, open the Command Palette (Ctrl+Shift+P) and select the Python: Select Linter command. The Select Linter command adds "python. ......
Read more >Improve your code with lint checks - Android Developers
The lint tool checks for structural code problems that could affect the quality and performance of your Android application. It is strongly recommended...
Read more >Show all warnings and errors in visual studio code
ES-Lint has introduced a new task in VS Code. You have to enable it in the workspace setings. "eslint.lintTask.enable": true. Just go ...
Read more >ESLint | WebStorm Documentation - JetBrains
To lint files from a specific folder, replace {**/*,*} with <path to the folder>* . Suppose, you have a project with the following...
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
Hoping to get some time to work on DC over the weekend, so will get this in for 2.1.
But, if anyone is looking for something to get their toes wet in the meantime, this would be a pretty easy first contribution! I included a diff above that turned it on always; all that’s needed is a new property adding to the
config
class (there are loads to copy) and then config.xxx adding to the condition above! (Oh, and the option adding to packages.config for the intellisense and the readme for an explanation).The contributing file was updated recently with a little more info on how it works and how to run it.
(Note: I’m not trying to fob this off, I just don’t know if people would like to contribute but don’t know where to start! 😃)
Yeah, seems like a reasonable idea. I’m not a fan of too many options (increases testing burden) but this is a pretty trivial change in behaviour!