Why does isNil
method in Lodash use null
instead of undefined
?
function isNil(value) { return value == null; }
Lodash helps in working with arrays, strings, objects, numbers, etc. The _. isNil() method is used to check if the value is null or undefined. If the value is nullish then returns true otherwise it returns false.
isUndefined() method is used to find whether the given value is undefined or not. It returns True if the given value is undefined.
To remove a null from an object with lodash, you can use the omitBy() function. If you want to remove both null and undefined , you can use . isNull or non-strict equality.
Lodash helps in working with arrays, strings, objects, numbers, etc. The _. isNull() method is used to find whether the value of the object is null. If the value is null then returns true otherwise it returns false.
It makes no difference either way in terms of the logic using null
or undefined
as null == undefined == true
, but using null
instead of undefined
would make the file size smaller by 5 bytes.
It's simply done to save a few bytes making the file smaller and faster to download from the server.
To understand this a bit better, it's important to note that lodash
is using ==
here instead of ===
.
Take the following example:
console.log(null == undefined); // true console.log(null === undefined); // false
By using ==
(double equals), lodash is utilizing type coercion where null
and undefined
will be coerced to falsy values. As a result, null == undefined
is true
.
However, if using ===
(triple equals), no coercion is enforced, which means the types must be identical, and as we know null
is not identical to undefined
. As a result, null === undefined
is false
.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With