Is there a consistent way to test for undefined and null in typescript 2.0?

Asked Apr 24 '17 at 17:21

Active Apr 24 '17 at 17:21

Viewed 126 times

So, I have several checks like this in my code:

if (callerParam != undefined || callerParam != null)

I now upgraded to Typescript 2.0 and Visual Studio is telling 'Cannot resolve symbol 'undefined''.

But the compare to null is just fine.

So I guess I can go change all my compares to be like this:

if (typeof callerParam !== 'undefined' || callerParam != null)

and the intellisense is OK with that.

But it seems inconsistent.

Is there a way to get my consistant, happy, world back?

And, why is undefined not valid anymore? And yet it is valid javascript right?

asked Apr 24 '17 at 17:21

Vaccano

1

Your answer could be found here http://stackoverflow.com/questions/28975896/is-there-a-dedicated-function-to-check-null-and-undefined-in-typescript – Alf Moh Apr 24 '17 at 17:24
@AlfMoh - Thanks for directing me! – Vaccano Apr 24 '17 at 18:19

0 Answers0