@@ -365,7 +365,7 @@ module.exports = {
365
365
] ,
366
366
367
367
// Disabled for now as it causes too many weird TypeScript issues. I'm not sure whether the problems are caused by bugs in TS or problems in my types.
368
- // TODO: Try to re-enable this again in 2023 .
368
+ // TODO: Try to re-enable this again in 2026 .
369
369
// '@typescript-eslint/method-signature-style': 'error',
370
370
371
371
// We use `@typescript-eslint/naming-convention` in favor of `camelcase`.
@@ -394,7 +394,7 @@ module.exports = {
394
394
}
395
395
] ,
396
396
397
- // TODO: Try to enable this again in 2023 .
397
+ // TODO: Try to enable this again in 2025 .
398
398
// Disabled for now. This is a great rule. It's just that TypeScript is not good enough yet to not use `any` in many places.
399
399
// For example: https://github.com/sindresorhus/refined-github/pull/2391#discussion_r318995182
400
400
// '@typescript-eslint/no-explicit-any': [
@@ -518,7 +518,7 @@ module.exports = {
518
518
// `no-unnecessary-condition` is essentially a stricter version of `no-constant-condition`, but that isn't currently enabled
519
519
'no-constant-condition' : 'error' ,
520
520
521
- // TODO: Try to enable this again in 2023 *if* the following are resolved:
521
+ // TODO: Try to enable this again in 2025 *if* the following are resolved:
522
522
// - https://github.com/microsoft/TypeScript/issues/36393
523
523
// - The rule needs a way to ignore runtime type-checks: https://github.com/sindresorhus/refined-github/pull/3168
524
524
// - Run the rule on https://github.com/sindresorhus/refined-github and ensure there are no false-positives
@@ -582,6 +582,7 @@ module.exports = {
582
582
}
583
583
] ,
584
584
'@typescript-eslint/prefer-as-const' : 'error' ,
585
+ '@typescript-eslint/prefer-find' : 'error' ,
585
586
'@typescript-eslint/prefer-for-of' : 'error' ,
586
587
'@typescript-eslint/prefer-function-type' : 'error' ,
587
588
'@typescript-eslint/prefer-includes' : 'error' ,
0 commit comments