From bbbf88972520e8af3439ba2ab3f1a1c40e68041c Mon Sep 17 00:00:00 2001
From: Sindre Sorhus <sindresorhus@gmail.com>
Date: Fri, 6 Sep 2019 01:13:34 +0700
Subject: [PATCH] Temporarily disable the `@typescript-eslint/no-explicit-any`
 rule

---
 index.js | 18 +++++++++++-------
 1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/index.js b/index.js
index d8c92a2..32b3b0e 100644
--- a/index.js
+++ b/index.js
@@ -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.
+		// 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.