This repository has been archived by the owner on Aug 31, 2023. It is now read-only.
[typescript] noExplicitAny rule is dumb (black/white config) #4167
c0ncentus
started this conversation in
Suggestions
Replies: 1 comment 3 replies
-
Hi :) You can disable the rule in the configuration file or add a |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
making error on playground.
I expect use "any" because expose as functionnality in typescript, it make sense on parameters only and very rare circonstance.
can you make an "any" mode : "authorizeOnParamater", "NoAny", "Any-way" mode please ?
if Rome ban all any because it is "any" then i should do this (very ugly).
but at the same I want detect all "any" in my code
When you convert .js to .ts, I used to have ~100 errors with gentle config,
have "superStrict">"strict">"gentle">"no config" configuration will help to prioritize ...
Then it will better I think to add more shades/tolerance to "any" errors .
Beta Was this translation helpful? Give feedback.
All reactions