Per this, there are many things that may go in the compilerOptions option at tsconfig.json, and noImplicitAny will throw errors at the compiler in a type is not declared in such a manner that TypeScript has to fall over to assuming a type of any. Explictly using any is OK, but the thing one is really trying to get away from here is "JavaScript in your TypeScript" in a not idiomatic way, even though TypeScript is a superset of JavaScript. That is, we are trying to make sure we are using types in TypeScript.
No comments:
Post a Comment