Some of the Typescript not respecting noImplicitAny from project tsconfig.json file

[brianjorden]

It seems there is a slightly inconsistent behavior of Typescript parsing and the usage of the project's local tsconfig.json settings. The part I've really noticed is the noImplicitAny flag being interpreted in some, but not all places. The screenshot below shows a couple arbitrary function definitions inside and outside a component's export default. Based on reading some of the comments in the Typescript pull request, it seems there are some assumptions that have to be made about the default export, and it might be tied to that. I've also included a couple declarations that show appropriate errors when the type IS given, so it is obviously trying to validate things. The difference is between thing2 and stuff2.

[octref]

Would you mind sharing the test project with me?

[octref]

Also see #159 (comment)

[octref]

I'll track this in #159.

[evenfrost]

Just faced this one recently. TypeScript checking with noImplicitAny is not working in .vue files for this specific case, but others do.

Tested on vue-cli with TypeScript config.

Here, VS Code outputs only 1 typechecking error (though event in onClick method has implicit any type):

However, TypeScript compiler correctly outputs 2 errors:

@octref as this issue and #159 are now closed, #170 is not quite related to TypeScript itself but to TSLint support and #188 seems to not have TypeScript-specific tasks in it, I just wanted to make sure this issue is still being tracked.