react-redux-links

Short version: React already knows what component instance it's rendering. Whenever a hook is called, React looks up the right data from a linked list stored in the internal component metadata objects. For more details, see: - Shawn Wang's talk "Getting Closure on Hooks": https://www.swyx.io/getting-closure-on-hooks/ - React Hooks Demystified: https://dev.to/kayis/react-hooks-demystified-2af6 - React Hooks - Not Magic, Just Arrays: https://medium.com/@ryardley/react-hooks-not-magic-just-arra... - additional articles: https://github.com/markerikson/react-redux-links/blob/master...

I gotcha covered there :) See my "Idiomatic Redux" blog post series [0] for info on how Redux was designed, why it works the way it does, and the implementation details of both the Redux core, React-Redux, and our new Redux Toolkit package. I also recommend the post "Build Yourself a Redux" [1] as the best "build a mini Redux" post I've seen. Rodrigo Pombo's "Didact" series [2] does the same process but for React, showing how to build a miniature reconciler that even includes hooks. I also have links to further articles about React's implementation [3] as well. Finally, I specifically recommend reading my post "A (Mostly) Complete Guide to React Rendering Behavior [4] and Dan Abramov's extensive article "A Complete Guide to `useEffect`" to better understand how React behaves and how to use it correctly. [0] https://blog.isquaredsoftware.c

For starters, I'd suggest going through Rodrigo Pombo's walkthrough "Build Your Own React" [0], my post "A (Mostly) Complete Guide to React Rendering Behavior" [1], Dan Abramov's treatise "A Complete Guide to `useEffect`" [2], and Shawn Wang's talk "Getting Closure on Hooks" [3]. I also have additional links on both React's internals [4] and React hooks specifically [5] that should be useful. [0] https://pomb.us/build-your-own-react/ [1] https://blog.isquaredsoftware.com/2020/05/blogged-answers-a-... [2] https://overreacted.io/a-complete-guide-to-useeffect/ [3] https://www.swyx.io/speaking/react-hooks/ [4] https://github.com/markerikson/react-redux-links/blob/master... [5] https://github.com/markerikson/react-redux-links/blob/master...

Not exactly. I'd strongly recommend reading through the React hooks docs, as well as the other hooks resources I have linked here: https://github.com/markerikson/react-redux-links/blob/master...

The ordering question is literally just about how you call them within a single specific component. That component can then be used as many times as you want, in as many apps as you want. In other words, this is not legal: const [stateA, setStateA] = useState(false); if(stateA) { const [stateB, setStateB] = useState(42); } Call as many hooks as you want, in whatever sequence you want. Just make sure all the calls are at the top level of that function component, and that you don't somehow change the sequence of those from one render pass to the next. As for how they work, React already has metadata that describes each component in the tree. There's a specific field in those metadata objects that gets used for tracking internal component state, and for function components, that field stores an array / linked list of

Hi, I'm a Redux maintainer. You may be interested in my suggested resources for learning React and Redux: https://blog.isquaredsoftware.com/2017/12/blogged-answers-le... https://blog.isquaredsoftware.com/2017/12/blogged-answers-le... https://github.com/markerikson/react-redux-links Also, please check out our new official Redux Toolkit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once. It's our recommended way to write Redux logic: https://redux-toolkit.js.org Meanwhile, we're working on a major rewrite of the Redux core docs. I'm hoping to put together a new "Quick Start" tutorial page that will show how to use Redux Toolkit and React-Redux in a "top-down" approach as a fast way to get productive.