Undefined and Null in *NgIf

Question

Are null, undefined and ""<empty string> value treated similarly by *Ngif? For example, is this: *ngIf = "foo == null"

Treated the same as: *ngIf = "foo == undefined"

If not, is there a simpler way to use *ngIf to not show properties with the value null, undefined, and ""?

Hey, `foo` itself considered a `false` **value**, use it directly *ngIF="foo" — Ashutosh Kumar, Jul 22 '20 at 04:20

score 2 · Accepted Answer · answered Jul 22 '20 at 04:00

2

You can simply check *ngIf = "foo" that can check undefined and null or empty.

answered Jul 22 '20 at 04:00

Adya

Sorry if I sound super ignorant, I'm a beginner in the world of coding. Is "foo" like a function? I thought it was simply a variable people like to use haha – Martin Pascual Jul 22 '20 at 04:02
1

Ow wait. I think I get what you mean now. Thanks! – Martin Pascual Jul 22 '20 at 04:04
Depends on how you are using it... I considered it as a variable. – Adya Jul 22 '20 at 04:04
@MartinPascual if it solves your problem then accept the answer also. – Adya Jul 22 '20 at 04:09

score 1 · Answer 2 · answered Jul 22 '20 at 04:01

1

You can solve this also by using

null === undefined // false
null == undefined // true

by the use of strict comparison operator

answered Jul 22 '20 at 04:01

Santa

2 Answers2