Skip to content

Conversation

github-actions[bot]
Copy link

Closes #412

Applied changes based on Issue #412.

I’ve added an ESLint override so that @typescript-eslint/no-explicit-any is turned off for all files in your __tests__ folder. This lets you continue using any in tests until you gradually tighten up type coverage.

Changes in this patch:

  • .eslintrc.js: added an overrides block targeting **/__tests__/**/*.{ts,tsx} to disable @typescript-eslint/no-explicit-any.
   },
-};
+  },
+  overrides: [
+    {
+      files: ['**/__tests__/**/*.{ts,tsx}'],
+      rules: {
+        '@typescript-eslint/no-explicit-any': 'off',
+      },
+    },
+  ],
+};

【F:.eslintrc.js†L87-L96】


With this in place, you can continue writing tests with any and incrementally replace them with more precise types (or unknown) over time. Let me know if you’d like any tweaks to the pattern or scope!

@YiweiShen YiweiShen merged commit ba47ee8 into main Jul 10, 2025
2 checks passed
@YiweiShen YiweiShen deleted the codez-chore-412-lint-handle-no-explicit-any-rule-in-tests-3055145583 branch July 10, 2025 02:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore(lint): handle @typescript-eslint/no-explicit-any in tests

1 participant