fix: rm empty object from @typescript-eslint/ban-types

Covered by @typescript-eslint/no-empty-object-type
mightyiam · Aug 24, 2024 · 79c1eaa · 79c1eaa
1 parent 28572d5
commit 79c1eaa
Show file tree

Hide file tree

Showing 2 changed files with 0 additions and 14 deletions.
diff --git a/src/index.ts b/src/index.ts
@@ -60,13 +60,6 @@ const rules = {
             '- If you want a type meaning "any value", you probably want `unknown` instead.',
           ].join('\n'),
         },
-        '{}': {
-          message: [
-            '`{}` actually means "any non-nullish value".',
-            '- If you want a type meaning "any object", you probably want `Record<string, unknown>` instead.',
-            '- If you want a type meaning "any value", you probably want `unknown` instead.',
-          ].join('\n'),
-        },
       },
     },
   ],

diff --git a/src/test/_expected-exported-value.ts b/src/test/_expected-exported-value.ts
@@ -220,13 +220,6 @@ export const expectedExportedValue: TSESLint.FlatConfig.Config = {
               '- If you want a type meaning "any value", you probably want `unknown` instead.',
             ].join('\n'),
           },
-          '{}': {
-            message: [
-              '`{}` actually means "any non-nullish value".',
-              '- If you want a type meaning "any object", you probably want `Record<string, unknown>` instead.',
-              '- If you want a type meaning "any value", you probably want `unknown` instead.',
-            ].join('\n'),
-          },
         },
       },
     ],