Re:Thinking in React Hooks
by ratww on Friday December 13, 2019 @07:08AM
(#21780878)
A regular global variable that is incremented each time you call useState/useEffect/etc and is resetted every time a new component starts rendering. This is why hook order must be maintained.
I have no idea where this is implemented in React, but in Preact it's a simple integer that is incremented:
I think there are other ways to implement them, such as treating the return of the render function as an AST and turning hooks into dumb factories, like a free monad. But considering the constraints they have (the need to maintain order) and the way it works (the fact the render function runs multiple times), I'm guessing it's just the same solution as Preact.
Re:Thinking in React Hooks
by brlewis on Friday December 13, 2019 @01:06PM
(#21783847)
Resetting it as render starts makes that number conceptually local to the vnode, even though preact's implementation involves a variable that's global in the context of that module.
I have no idea where this is implemented in React, but in Preact it's a simple integer that is incremented:
https://github.com/preactjs/preact/blob/abc162c4d6442d5495f6...
I think there are other ways to implement them, such as treating the return of the render function as an AST and turning hooks into dumb factories, like a free monad. But considering the constraints they have (the need to maintain order) and the way it works (the fact the render function runs multiple times), I'm guessing it's just the same solution as Preact.