Description
Hi! Sophia pinged me as you were starting your talk, and I was able to watch almost all of it via the livestream. That was an excellent talk!
I'm one of the maintainers of Redux, and also participated in the discussion in reduxjs/react-redux#210 . You bring up some very interesting points regarding child components rendering after a parent dispatches in a lifecycle method.
The one question I have off the top of my head is, does this issue still reproduce in React-Redux 5.x, or only in 4.x? Taking a look at this repo's project.json
, I do see that it's using 4.x, so I'd be curious if that makes a difference.
As you said, the lifecycle/dispatch/rendering sequence is not really a bug per se, but sort of a fallout of a couple specific known behaviors.
I don't have too much specific to discuss at the moment, but given that you've clearly spent time looking into this issue and thinking about it, I'd absolutely love to have any feedback you can offer regarding possible improvements to React-Redux, especially once React Fiber starts going asynchronous.
Pinging @timdorr, @jimbolla, and @naw , since they were involved in the discussion in 210.