dan

>The Fast Refresh (from react/refresh) only re-run the variable Component (the first capitalized), That's expected. React component names must always start with a capital letter. This convention is assumed by...

Can somebody please help me understand: is the problem strictly in extra `onChange` calls *in the middle*? Or do you get incorrect value in the end?

The test from the fix attempt in https://github.com/facebook/react/pull/8438 passes if I remove the assertion about the number of times `onChange` is called. So I suppose this issue is only about...

@crochefluid Can you create a failing test for this? Similar to what #8438 tried to do. In that test, there was no incorrect value.

It’s a Node test but it encodes sequences captured from different browsers and devices. Please see its source. You’d need to add sequences that are failing.

What are the exact reproduction steps? It’s not obvious what you’re doing, what you’re seeing, and what you’re expecting to see. Please be precise.

The reason plugin sees it differently is because **by doing `props.whatever()` you are actually passing `props` itself as a `this` value to `whatever`**. So technically it would see stale props....

Is there a problem with destructuring those early? That’s the solution.

@zzzachzzz >Another use case affected by this is when using `useReducer` for state in a component. It's common to use a single `state` object with `useReducer`, making it necessary to...

>It's like doing using namespace std; in C++, which is bad practice. I don't think this is an accurate comparison. Destructuring props doesn't bring random things in scope. It only...