noImplicitAny not respected? about create-react-app-typescript HOT 8 CLOSED

This suppressImplicitAnyIndexErrors shouldn't probably be true by default. Why should it be? It suppresses quite bad errors, i.e.:

const key = 'someString';
const value: boolean = false;
const result = value[key]; // would be highlighted if `suppressImplicitAnyIndexErrors` weren't true

from create-react-app-typescript.

Hm something else is wrong, the tsconfig.json is read (if I break it things won't compile)

from create-react-app-typescript.

Looks like it works if I directly invoke tsc:

~/GitHub/my-app$ ./node_modules/typescript/bin/tsc --noImplicitAny --jsx react src/App.tsx
src/App.tsx(8,11): error TS7017: Element implicitly has an 'any' type because type 'X' has no index signature.

from create-react-app-typescript.

Any update on this? I'm surprised that nobody else using this package has reported the same issue.

from create-react-app-typescript.

@wmonk I just tried the repro steps and still doesn't work for me. Does it work for you?

from create-react-app-typescript.

Looks like the generated tsconfig.json is explicitly suppressing that error with

    "suppressImplicitAnyIndexErrors": true,

from create-react-app-typescript.

Oh I'm blind.. yes you're right, that explains everything. Thank you @tko!

from create-react-app-typescript.

Why maintain suppressImplicitAnyIndexErrors set to true by default? Could anyone point me to some resource on the reasoning behind it?

In what case is it better to suppress this kind of warning?

from create-react-app-typescript.