Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add `requireConfig`-like option to only run eslint if it's configured
See original GitHub issueCurrently, when I work inside projects, that don’t have eslint set up, it always runs (and marks a lot of things as errors / warnings), as it’s not configured properly.
One solution to this may be something like prettier-vscode’s prettier.requireConfig option.
It prevents prettier from formatting files if prettier is not configured in a workspace.
Would it be possible / feasible to have something like that for vscode-eslint, or is there already a solution which I’m not aware of?
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
There is a deprecated setting
eslint.enable. The recommended way to do this in VS Code is to disable the extension for the workspace folder using the extensions viewlet.ok nevermind, not big of an issue