I am trying to figure out if it is possible to handle multiple levels of default parameters with destructuring. Since it is not easy to explain with words, here is a step-by-step example...
Destructuring this object is easy:
let obj = {
foo: 'Foo',
bar: 'Bar'
};
With {foo = 'Foo', bar = 'Bar'} = {}
in a function signature, an object will be created if there is no argument passed when the function is called. If an object is passed but some referenced properties are undefined
, they will be replaced by their default values. This code works fine:
function fn1({foo = 'Foo', bar = 'Bar'} = {}) {
console.log(foo, bar);
}
// OK
fn1(); // Foo Bar
fn1({foo: 'Quux'}); // Quux Bar
fn1({bar: 'Quux'}); // Foo Quux
fn1({foo: 'Quux', bar: 'Quux'}); // Quux Quux
Destructuring this object is harder:
let obj = {
foo: 'Foo',
bar: {
quux: 'Quux',
corge: 'Corge'
}
};
{foo = 'Foo', bar = 'Bar'} = {}
is not a viable option anymore, but now we can use {foo = 'Foo', bar = {quux: 'Quux', corge: 'Corge'}} = {}
in a function signature. Again, if no argument is given when the function is called, an object is created and the core properties (foo
and bar
) are extracted. If an object is passed, only undefined properties (foo
or bar
) will be destructured with their default values.
The problem is that the object properties of bar
(quux
and corge
) are not part of the "top-level destructuring". This means quux
or corge
will be undefined
if they are not explicitly set when bar
is passed as an argument:
function fn2({foo = 'Foo', bar = {quux: 'Quux', corge: 'Corge'}} = {}) {
console.log(foo, bar.quux, bar.corge);
}
// OK
fn2(); // Foo Quux Corge
fn2({foo: 'Quux'}); // Quux Quux Corge
// Oops!
fn2({bar: {quux: 'Baz'}}); // Foo Baz undefined
fn2({foo: 'Quux', bar: {corge: 'Baz'}}); // Quux undefined Baz
I would like to set default parameters at all levels of the object hierarchy to use a sort of "cascading destructuring". I tried this, but it does not work:
function fn3({foo = 'Foo', bar = ({quux = 'Quux', corge = 'Corge'} = {})} = {}) {
console.log(foo, bar.quux, bar.corge);
}
// Oops!
fn3(); // Foo undefined undefined
fn3({foo: 'Quux'}); // Quux undefined undefined
fn3({bar: {quux: 'Baz'}}); // Foo Baz undefined
fn3({foo: 'Quux', bar: {corge: 'Baz'}}); // Quux undefined Baz
Do you know if such a feature is allowed in ES6. If yes, how can I implement it?
Destructuring nested objectsIf we need to access an employee's info we can destructure as many levels as it takes to get to our employee object's properties. const { engineers: { 1: { id, name, occupation, }, }, } = employees; Now we have access to all of the second employee object's properties.
JavaScript destructuring, nested and otherwise, is a nice shorthand to allow us to quickly define variables from values in a collection, object, or array. We can use it with rest syntax to assign remaining elements a variable. We can rename the elements that we pull out to a variable name of our choosing.
To destructure an array in JavaScript, we use the square brackets [] to store the variable name which will be assigned to the name of the array storing the element. const [var1, var2, ...]
The generic pattern for destructuring object properties is
{ … , propertyName: target = defaultInitialiser, … }
(when the property name is exactly the same as the target variable identifier we can join them).
But target
is not only for variables, it can be any assignment target - including nested destructuring expressions. So for your case (3) you want to use exactly the same approach as with (1) on the top level of the parameter - default initialise the property with an empty object and destructure its parts:
function fn3({foo = 'Foo', bar: {quux = 'Quux', corge = 'Corge'} = {}} = {}) {
console.log(foo, quux, corge);
}
Notice that there is no bar
variable when you destructure that property. If you want to introduce a bar
variable for the property as well, you could repeat the property name and do
function fn3({foo = 'Foo', bar, bar: {quux = 'Quux', corge = 'Corge'} = {}} = {}) {
console.log(foo, bar, quux, corge);
}
I've got something that's a little simpler. It has drawbacks. But first, the goods:
function doit( arg1 = 'one', hash = { prop1: 'two', prop2: 'three' }, { prop1, prop2 } = hash ) {
console.log(`arg1`, arg1)
console.log(`prop1`, prop1)
console.log(`prop2`, prop2)
console.log(`hash`, hash)
}
What does this accomplish?
How does it work?
ES6 parameter defaults can refer to other parameters, like so:
function math( x = 1, y = x ) { ... }
// x = 1
// y = 1
So, even though the example function is designed to accept two arguments (arg1
and hash
), the signature is formally declared with three arguments. The third argument is a kind of fictional or temporary argument that exists solely for the purpose of destructuring hash
. It is the logical equivalent of this:
function doit( arg1 = 'one', hash = { prop1: 'two', prop2: 'three' } ) {
let { prop1, prop2 } = hash
...
}
The virtue of this pattern is that the signature is completely self-documenting. It's sadly very common in JS to see signatures declared like this:
function terminateEmployee( employeeId, options ) {
// what properties does `options` accept??
}
To answer that question, you need to search all downstream codepaths and collect every use of options
. Sometimes that codepath is really long; if you're unlucky enough to be working in a microservice-based ecosystem, that codepath can span two or more additional codebases in other languages (true story).
Yes, we can ask devs to write documentation, but YMMV on that score.
So, this pattern allows the implementation to be self-documenting, without relying on extra documentation that devs would need to write and maintain.
The downside is that the function looks like it accepts three arguments -- and it really does accept three. So, devs who are unaware of what's going on can be misled. And, if a caller passes three args, the third arg will override the second arg.
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