Strict equality and loose equality with logical and operator

Asked Mar 16 '19 at 23:44

Active Mar 16 '19 at 23:53

Viewed 18 times

Is it considered a bad practice to combine a loose equality check (foo != null) with a strict equality check (bar === true)?

In my opinion, they should both be compared with the strict equality, or both be compared with the loose equality check.

Is there ever a scenario where I would need to have a loose equality check combined with a strict equality check?

Thanks Stackoverflow!

Looking forward to your insight!

const foobar = foo != null && bar === true;

Edit, this question differs from Which equals operator (== vs ===) should be used in JavaScript comparisons? because, this is particularly on combining a loosely equal comparison with a strict equal comparison. This stack overflow question referenced above is only in conjunction with using one or the other.

I am particularly interested if its ever a valid use case to use both a loose equal, with a strict equal inside a comparison.

edited Mar 16 '19 at 23:53

asked Mar 16 '19 at 23:44

Peter Tran

1

It's not the *combination* of them that's the issue, it's the use of loose equality *at all* IMO – CertainPerformance Mar 16 '19 at 23:45
i agree with @CertainPerformance. if your code requires the use of loose equality there is a fundamental problem in your design. – Chris Rollins Mar 16 '19 at 23:46
1

Loose equality is very useful for comparing to `null` because it includes `undefined` and nothing else. Doing `foo != null` is so much nicer than `foo !== null && foo !== undefined`. – ziggy wiggy Mar 16 '19 at 23:53
@ziggywiggy ahh I see. That makes total sense! Thank you. – Peter Tran Mar 16 '19 at 23:53
Yep, you're welcome. – ziggy wiggy Mar 16 '19 at 23:54

Strict equality and loose equality with logical and operator

0 Answers0