Configuration for rule "@typescript-eslint/ban-ts-comment" is invalid
See original GitHub issueHey, I’m getting the following error when launching eslint through the command line:
$ npx eslint src --fix
.eslintrc.js#overrides[1]:
Configuration for rule "@typescript-eslint/ban-ts-comment" is invalid:
Value "allow-with-description" should be boolean.
This seems to stop the linting completely. I thought manually overriding the rule should help, but it doesn’t:
module.exports = {
extends: 'galex',
rules: {
'@typescript-eslint/ban-ts-comment': 0,
},
};
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
[ban-ts-comment] Seemingly valid configuration is being ...
[ban-ts-comment] Seemingly valid configuration is being flagged as invalid · Issue #2157 · typescript-eslint/typescript-eslint · GitHub.
Read more >ban-ts-comment - TypeScript ESLint
Disallow `@ts- ` comments or require descriptions after directives. ... This rule lets you set which directive comments you want to allow in...
Read more >how ignore typescript errors with @ts-ignore? - Stack Overflow
EDIT: If you are using @typescript-eslint/eslint-plugin version 2.18 or higher, the rule is called ban-ts-comment and you need to add
Read more >How to Use @TypeScript-ESLint/Ban-TS-Comment
If you are using TypeScript and TypeScript-ESLint in a team setting, you can ban TypeScript comments by adding the @typescript-eslint/ban-ts- ...
Read more >Rules - ESLint - Pluggable JavaScript Linter
Some problems reported by this rule are automatically fixable by the --fix command ... Disallow invalid regular expression strings in `RegExp` constructors.
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
It didn’t! The other errors had gone away.
Wow, that was fast. All works well with the latest update, thank you<. Just to be sure, when’d like to disable
import/no-namespace
, for example, in all files, I can simply haveIs that right? And the overrides are needed only when I’d like to cherrypick in which files the rule gets enforced.