This wouldn't be 100 percent reliable since 0, empty string, and NaN are also falsy.
So you would get the second choice returned in those cases as well.
Yea, i guess you could just use the snippet if you wanted to check if theres really a value or not. I think it could be useful sometimes when you are getting a value from an api and you don't have access into the backend funtions, and they just throw either undefined null 0 or empty string
My view is to have undefined something only the runtime is allowed to set, while null is something I deliberately set.
This way you get a hint who messed up if the value is missing.
As long as we remember the difference, I think it's OK. Also, we have to be consistent in how we use them.
Some comments have been hidden by the post's author - find out more
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.