mirror of
https://github.com/mauriceboe/TREK.git
synced 2026-10-18 21:16:47 +00:00
07f35d8b81
eslint.config.mjs keeps most rules at warn so that CI stayed green on a codebase that was never linted, and CI runs eslint without --max-warnings. Warnings therefore only ever accumulated: 1218 today, among them 194 unused variables and 144 missing effect dependencies in app code, the kind behind the stale closures #2610 chased. lint:warnings runs ESLint over the client with its own config and counts the warnings per rule, separately for app code and for tests, so the headroom from fixing a test cannot be spent in app code. Messages that an eslint-disable comment silenced are counted as a third group, so an inline disable is no way past the ratchet either. No count may pass its entry in scripts/eslint-baseline.json, and --update only lowers. Any error, a parse failure included, fails the check too, so it can replace the plain lint:check step in CI instead of running ESLint twice.
26 lines
757 B
JSON
26 lines
757 B
JSON
{
|
|
"src": {
|
|
"@typescript-eslint/no-explicit-any": 174,
|
|
"@typescript-eslint/no-unused-expressions": 4,
|
|
"@typescript-eslint/no-unused-vars": 194,
|
|
"no-empty": 34,
|
|
"no-useless-assignment": 7,
|
|
"no-useless-escape": 1,
|
|
"preserve-caught-error": 53,
|
|
"react-hooks/exhaustive-deps": 144,
|
|
"react-refresh/only-export-components": 48,
|
|
"unused-disable-directive": 7
|
|
},
|
|
"suppressed": {
|
|
"@typescript-eslint/no-explicit-any": 50,
|
|
"react-hooks/exhaustive-deps": 64
|
|
},
|
|
"tests": {
|
|
"@typescript-eslint/no-explicit-any": 494,
|
|
"@typescript-eslint/no-this-alias": 1,
|
|
"@typescript-eslint/no-unsafe-function-type": 2,
|
|
"@typescript-eslint/no-unused-vars": 54,
|
|
"react-refresh/only-export-components": 1
|
|
}
|
|
}
|