
…ect would always update regardless of whether it was listening to the state slice that got updated. This particular problem was the reason react-redux had to release a new major version (namely 7.x.x), in which it re-wrote the code, decoupled itself from the previous Context API implementation …ect would always update regardless of whether it was listening to the state slice that got updated. This particular problem was the reason react-redux had to release a new major version (namely 7.x.x), in which it re-wrote the code, decoupled itself from the previous Context API implementation and w…
s of whether your c…xisting library that allowed you to utilise things like useRedux or useConnect wasn’t able to solve a crucial performance related issue, that caused your hooked component to re-render any time any piece of state changed, regardless of whether your component listened to this particular piece of state or not. This is because the 6.x.x. version of react-redux attempted to fully utilise the new React Context …
…w React Context API which unfortunately has no render bail-out techniques. What this means, is that anytime a Context.Provider updates, then every Context.Consumer would have to update as well. Thus, any component that a hook like useRedux or useConnect would …w React Context API which unfortunately has no render bail-out techniques. What this means, is that anytime a Context.Provider updates, then every Context.Consumer would have to update as well. Thus, any component that a hook like useRedux or useConnect would always update regardless of whet…