`mapStateToProps` should not be called with functional component rendering a connected class component
Author: pandaioloCreated Jun 5, 2023Updated May 21, 2026
What version of React, ReactDOM/React Native, Redux, and React Redux are you using?
- React: 18.2.0
- ReactDOM: 18.2.0
- Redux: 4.2.1
- React Redux: 8.0.5
What is the current behavior?
Description:
- Depending on a parent component being a functionnal or class component, children connected component do not see their
mapStateToPropsfunction called in the same way
Reproduction:
- https://codesandbox.io/s/beautiful-gianmarco-wo67u0
- Click on toggle and check the console logging
- we can see a call to
mapStateToPropsin the class component child, when the parent component is a functional component ([APP1]) but not when the parent is a class component ([APP2])
Here is the logging, by app, when toggling off connected children (conditional rendering):
With a functional component as parent:
[APP1] CLASS CHILD MAP STATE TO PROPS
[APP1] NORMAL CHILD SELECTOR
x2 [APP1] NORMAL PARENT SELECTOR
[APP1] RENDER PARENT {showChild: false}
[APP1] NORMAL PARENT SELECTOR
[APP1] RENDER PARENT {showChild: false}With a class component as parent:
[APP2] CLASS PARENT MAP STATE TO PROPS
x2 [APP2] RENDER PARENT {showChild: false}
[APP2] NORMAL CHILD SELECTORNote:
- FYI this led to an issue in our code when refactoring a component, with uncaught error in the
mapStateToPropsfunction of a child of that component, because suddenly it was being called with unexpectedstateand trying to get state on undefined keys.
Maybe all of this is a normal consequence of the inherent difference in React rendering functional or class component, but I still wanted to document this in an issue for the record, and see if you have any comment.
Thanks!
What is the expected behavior?
mapStateToPropsshould be called consistently (or should it not?)
Which browser and OS are affected by this issue?
Chrome OSX
Did this work in previous versions of React Redux?
- Yes
Source: reduxjs/react-redux