feat(eslint-plugin): add no-unsafe-any #1374
Closed
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.
Fixes #791
WIP
any
any
generics to stricter ones (const x: Set<string> = new Set<any>([false]);
)any
)???New rule which uses type information to validate that you're not doing anything with an
any
.It's easy to keep your own code (mostly) safe via the
no-explicit-any
rule, but there are a number of places where things can get unsafe due to library types (from DefinitelyTyped, or from the default TS libraries).This rule will help catch of those cases.