chore(lint): handle no-explicit-any rule in tests #418
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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 usingany
in tests until you gradually tighten up type coverage.Changes in this patch:
overrides
block targeting**/__tests__/**/*.{ts,tsx}
to disable@typescript-eslint/no-explicit-any
.【F:.eslintrc.js†L87-L96】
With this in place, you can continue writing tests with
any
and incrementally replace them with more precise types (orunknown
) over time. Let me know if you’d like any tweaks to the pattern or scope!