Skip to content

Commit

Permalink
Temporarily disable the @typescript-eslint/no-explicit-any rule
Browse files Browse the repository at this point in the history
  • Loading branch information
sindresorhus committed Sep 5, 2019
1 parent 3202fed commit bbbf889
Showing 1 changed file with 11 additions and 7 deletions.
18 changes: 11 additions & 7 deletions index.js
Expand Up @@ -152,13 +152,17 @@ module.exports = {
allowSingleExtends: true
}
],
'@typescript-eslint/no-explicit-any': [
'error',
{
fixToUnknown: true,
ignoreRestArgs: true
}
],

// TODO: Try to enable this again in 2021.

This comment has been minimized.

Copy link
@kevva

kevva Sep 11, 2019

Don't hold your breath.

This comment has been minimized.

Copy link
@sindresorhus

sindresorhus Sep 12, 2019

Author Member

I'm not. It says "try". 😛

// 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.
// For example: https://github.com/sindresorhus/refined-github/pull/2391#discussion_r318995182
// '@typescript-eslint/no-explicit-any': [
// 'error',
// {
// fixToUnknown: true,
// ignoreRestArgs: true
// }
// ],

// Disabled because it's buggy. It transforms `...(personalToken ? {Authorization: `token ${personalToken}`} : {})` into `...personalToken ? {Authorization: `token ${personalToken}`} : {}` which is not valid.
// TODO: Report this issue.
Expand Down

0 comments on commit bbbf889

Please sign in to comment.