Skip to content

Commit

Permalink
feat: Disable "no-warning-comments"
Browse files Browse the repository at this point in the history
Todo/Fixme/Quickfix comments are not bad per se.
If teams want to use them this shouldn't be prevented.
There is also tooling support in editors which can filter/search these comment. Combined with such tooling this can be a good way to annotate code parts, especially during active development.
  • Loading branch information
Simon authored Mar 9, 2020
1 parent f35da72 commit 460f385
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions base.js
Original file line number Diff line number Diff line change
Expand Up @@ -460,12 +460,12 @@ module.exports = {
"no-var": "warn", // http://eslint.org/docs/rules/no-var
"no-void": "off", // http://eslint.org/docs/rules/no-void
"no-warning-comments": [
"warn",
"off",
{
location: "anywhere",
terms: ["todo", "fixme", "quickfix"],
},
],
], // http://eslint.org/docs/rules/no-warning-comments
"no-whitespace-before-property": "warn", // http://eslint.org/docs/rules/no-whitespace-before-property
"no-with": "warn", // http://eslint.org/docs/rules/no-with
// Non-block statements are disallowed anyway
Expand Down

0 comments on commit 460f385

Please sign in to comment.