I often run into this scenario where in need of a portion of an object. destructuring surely helps in grabbing what is needed. the annoyance occur when the portion is used as a new object - forcing the code to like this:
this is a duplication of the properties and is a pitfall in some cases where you might leave out few properties unwillingly (when it comes to large portions from large objects).
a syntax such as the following might achieve better stability, assurance and nonrepetitive code.
it's currently possible to gather the rest of unmentioned properties with {...rest} but I think in most cases it is way more essential to select and group the destructured properties.
Hi, I've came across this issue and I'm also interested in it. Is there any way I can start help contribute to this proposal? Maybe I can help draft the stage-0 version of the as-proposal which is based on zkat's version.