You know instead of:
const getObj = (id, store) => { return { id } }
const getObj = (id, store) => ({ id })
Re:Overview of JavaScript ES6 features
by i__believe on Monday October 24, 2016 @07:35PM
(#12783873)
I'm pretty sure that's a good illustration of my point.
This is a matter of personal preference.
I find `return` to be quite distracting and annoying for a small function that spans part of a line, while you and some others may prefer the explicitness of the `return` keyword.
I would agree that nested destructuring should be used quite cautiously. Code legibility is incredibly important to the success of any serious project.
const getObj = (id, store) => { return { id: id name: store.something.name }; };
The linter gave an error on it because I used {id: id}. It was like the linter was trying to make my code harder to read.
I think es6 in the wrong hands quickly falls prey to the problems of ruby/scala where it can become incredibly terse and hard to parse unless you are used to the author's particular style.