dan
@lewisblackwood >It's definitely possible to destructure earlier, but in a lot of cases that requires introducing intermediate aliases to avoid name clashing, when the things we're trying to access is...
Oops, didn't mean to close. I'm curious to hear if people who commented so far still find this to be a significant issue, or if they have mostly moved onto...
> It asks for the whole object when I'm only using one field. This is because you’re *assigning* to that object. It doesn’t make sense to depend on a field...
Can you share some examples of how you'd use it? Meaning concrete examples where you want `.current` to be a dependency. I'd like to better understand the scenarios you're describing.
Thanks for explaining the use case. This is a known inconvenience. Internally we’ve seen people make a custom `useEffectRef` Hook that does what you suggest. The current built-in canonical solution...
FYI, `16.0.0-alpha` is not representative of what will end up in 16. We only cut the release to test some changes related to React Native.
There's no definitive list because we're working on a complete rewrite of the reconciler ("Fiber"—see the [talk](https://youtu.be/aV1271hd9ew), [some info](https://github.com/acdlite/react-fiber-architecture), [progress](http://isfiberreadyyet.com/), [some more info](https://github.com/facebook/react/issues/7942), [more detailed progress](https://github.com/facebook/react/issues/7925)), and it is not...
Just to set expectations, we’ve considered all these options a few months ago and decided against them at the time. I’ll keep this open so we can later provide a...
Why does it matter if it executes once or twice? Since any function inside useMemo should be pure, it should make no difference. Is this a performance concern, or does...
>So any fix to this issue? There is no *issue* here per se. As explained on [this page](https://reactjs.org/warnings/invalid-hook-call-warning.html), React needs `useState()` calls to be on the same `react` object as...