destructuring

Closed . This question is opinion-based . It is not currently accepting answers. Want to improve this question? Update the question so it can be answered with facts and citations by editing this post . Closed 3 years ago . Somewhat new to ES6 modules and find myself torn between the following 2 patterns... Pattern #1 - Destructuring on import import { func1, func2, func3 } from 'my-funcs'; Pattern #2 - Destructuring on const import * as myFuncs from 'my-funcs'; const { func1, func2, func3 } = myFuncs; I like the pattern #1 for its brevity, but I also like pattern #2 as it seems more explicit.

EDIT: I opened an issue related to this on github: https://github.com/Microsoft/TypeScript/issues/21265 It seems that { ...other: xother } is not valid JS, neither TS, code and it should not even compile. Original question: Let's assume the following example: const values = { a: "1", b: "2", c: "3", d: "4" }; const { a: va, b: vb, ...other } = values; where a new variable name va is assigned for property a . Is it valid, according to TypeScript specs, to do the same with the remaining properties ...other ? Something like: const { a: va, b: vb, ...other: vother } = values; I know it works, I've

This question already has an answer here: ES6 Object Destructuring Default Parameters 1 answer When destructuring objects, I sometimes run into the issue of not knowing whether or not keys exist, and then trying to pull values from them. This obviously errors, since they are undefined. For example: Expecting something like this: { user: { name: { first: 'Trey', last: 'Hakanson' } } } But I actually get this: { user: {} } and attempting to destructure like this errors: const { user: { name: { first: firstName, last: lastName } } } = data is there any way to assign a default value earlier in the

I have an object const complicatedObject = { propertyA: { property1: 1, property2: 2 }, propertyB: { property1: 1, property2: 2 } } If I want to grab propertyA I do const { propertyA } = complicatedObject console.log(propertyA) // { property1: 1, property2: 2} If I want to grab propertyA's property1 value I do const { propertyA: { property1 } } = complicatedObject console.log(property1) // 1 I can grab propertyA and propertyA's property1 this way. const { propertyA, propertyA: { property1 } } = complicatedObject console.log(propertyA) // { property1: 1, property2: 2} console.log(property1) //

In official react-native documentation there is a section about Animated.event method. As example they use following code: onScroll={Animated.event( // scrollX = e.nativeEvent.contentOffset.x [{ nativeEvent: { contentOffset: { x: scrollX } } }] )} I would like to map correct values to Animated.event method and I would also like to map onScroll callback parameters to my own callback. Basically I would like to do something like this: onScroll={(event) => { myOwnCallback(event.nativeEvent.contentOffset.x) Animated.event( // scrollX = e.nativeEvent.contentOffset.x [{nativeEvent: { contentOffset: {

In Chrome version ^72 if I run the following JavaScript there are no errors. { prop: p } = { prop: 'prop' } >> { prop: 'prop' } So the line of code is interpreted as an expression statement, unexpectedly. But if I run the same code with a semi-colon at the end it runs as expected. { prop: p } = { prop: 'prop' }; >> Uncaught SyntaxError: Unexpected token = This is expected since the initial { tells the JavaScript engine that it is a code block unless we disambiguate with parentheses. Why does this occur with the semi-colon but not without it? Why does this occur with the semi-colon but not