Typescript throws no error when calling nullable function

Question

I have the following code in my react app:

As you can see onCheck can be undefined. but typescript shows no error and I'm getting a runtime error.

I have to add this prop has no default value.

My tsconfig:

{
    "compileOnSave": false,
    "compilerOptions": {
        "sourceMap": true,
        "target": "es5",
        "module": "esnext",
        "declaration": false,
        "noImplicitAny": false,
        "experimentalDecorators": true,
        "noLib": false,
        "jsx": "react",
        "noEmitOnError": true,
        "moduleResolution": "node",
        "lib": [
            "DOM",
            "ES5",
            "ScriptHost",
            "ES2015",
            "ES2018.Promise"
        ],
        "allowSyntheticDefaultImports": true
    },
    "exclude": [
        "node_modules"
    ]
}

Lazar Ljubenović · Accepted Answer · 2021-05-15 07:03:55Z

2

Under compilerOptions, add "strict": true in your tsconfig.json.

From the docs:

The strict flag enables a wide range of type checking behavior that results in stronger guarantees of program correctness. Turning this on is equivalent to enabling all of the strict mode family options, which are outlined below.

alwaysStrict

strictNullChecks

strictBindCallApply

strictFunctionTypes

strictPropertyInitialization

noImplicitAny

noImplicitThis

If you only care about the nullable variables, then just use the "strictNullChecks" flag.

answered May 15, 2021 at 7:03

Lazar Ljubenović

19.9k10 gold badges58 silver badges95 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

derpirscher · Accepted Answer · 2021-05-15 07:10:43Z

2

You don't have the according compiler option set in your tsconfig.json

Either add

"strictNullChecks": true

to just enable the null checks, or (recommended) add

"strict": true

to add a wide range of checks.

Be aware that using "strict": true may break your build when you upgrade the typescript version. Because new strict... flags will be switched on with that flag automatically.

answered May 15, 2021 at 7:10

derpirscher

17.7k3 gold badges25 silver badges54 bronze badges

Collectives™ on Stack Overflow

Typescript throws no error when calling nullable function

2 Answers 2

Comments

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Related