While developing my react App, I needed to send a conditional prop to a component so I found somewhere a pattern to do so, although it seems really weird to me and I couldn't understand how and why it worked.
If I type:
console.log(...undefined) // Error
console.log([...undefined]) // Error
console.log({...undefined}) // Work
When the spread operator is activated on undefined an error is raised, although when the undefined is inside an object, an empty object returned.
I'm quite surprised regarding this behavior, is that really how it supposed to be, can I rely on this and is that a good practice?
As you can see, no errors - the object-spread operator safely ignored the null and undefined argument, leaving us with a working clone of the target.
So the answer is: null and undefined values are just fine when spreading on a React element.
For nested objects the spread operator will provide a deep copy to the first instance of the values but leaves all the nested data as shallow copies sharing a space in memory with original.
JavaScript ES6 (ECMAScript 6) introduced the spread operator. The syntax is three dots(...) followed by the array (or iterable*). It expands the array into individual elements. So, it can be used to expand the array in a places where zero or more elements are expected.
This behavior is useful for doing something like optional spreading:
function foo(options) {
const bar = {
baz: 1,
...(options && options.bar) // options and bar can be undefined
}
}
And it gets even better with optional chaining, which is in Stage 4
now (and already available in TypeScript 3.7+):
function foo(options) {
const bar = {
baz: 1,
...options?.bar //options and bar can be undefined
}
}
a thought: its too bad it doesn't also work for spreading into an array
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