Skip to content

Commit

Permalink
Set eslint rules to warn only
Browse files Browse the repository at this point in the history
we should clean up the issues behind those warnings and set the rules back to the recommended . Changing it to warn now only to limit the scope of the PR and not having to touch legacy code.
  • Loading branch information
AliceR committed Dec 16, 2024
1 parent 6bc2ed0 commit b3a4c4f
Showing 1 changed file with 7 additions and 3 deletions.
10 changes: 7 additions & 3 deletions .eslintrc
Original file line number Diff line number Diff line change
Expand Up @@ -74,6 +74,7 @@
"react/no-unsafe": 2,
"react/no-unused-prop-types": 2,
"react/no-unused-state": 2,
"react/prop-types": 1,
"react/self-closing-comp": 2,
"react/sort-comp": 2,
"react/style-prop-object": 2,
Expand All @@ -92,13 +93,16 @@
"plugins": ["@typescript-eslint"],
"rules": {
"prettier/prettier": [
1,
"warn",
{
"parser": "typescript"
}
],
"@typescript-eslint/no-unused-vars": 2,
"@typescript-eslint/no-non-null-assertion": 0
"@typescript-eslint/no-explicit-any": "warn",
"@typescript-eslint/no-invalid-void-type": "warn",
"@typescript-eslint/no-non-null-assertion": "warn",
"@typescript-eslint/no-unused-expressions": "warn",
"@typescript-eslint/no-unused-vars": "warn"
},
// Weird behavior with no-unused-vars
// See https://stackoverflow.com/a/58513127
Expand Down

0 comments on commit b3a4c4f

Please sign in to comment.