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.
No way to disable issues with comments
See original GitHub issueTell us about your environment
- ESLint Version: N/A
- Node Version: v12.5.0
- npm Version: 6.13.0
What parser (default, Babel-ESLint, etc.) are you using?
Default with xo.
Please show your full configuration:
Configuration
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
// eslint-disable-next-line capitalized-comments
/* spell-checker: disable */
xo --quiet
What did you expect to happen?
capitalized-comments to apply to the comment below it.
What actually happened? Please include the actual, raw output from ESLint.
✖ 131:31 capitalized-comments rule is disabled but never reported. eslint-comments/no-unused-disable
If I remove the eslint-disable-next-line line then I get this.
✖ 131:31 Comments should not begin with a lowercase character. capitalized-comments
Are you willing to submit a pull request to fix this bug? Possibly?
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 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
@OmgImAlexis Is there any chance you could make a minimal reproduction case repo? It’s tough to know what’s going on with all the moving parts at the moment.
Hi, this may not be related to ESLint directly, but rather with the eslint-plugin-eslint-comments dependency used by xo. This dependency is the one that actually reports this error in xo