Add ownProps to mapStateToProps and mapDispatchToProps as second parameter #59
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jhollingworth
force-pushed
the
pass-in-props
branch
from
83588fd to
183a595
Compare
|
Good stuff. I'll merge today. ❤️ |
gaearon
added a commit
that referenced
this pull request
Aug 17, 2015
Add ownProps to mapStateToProps and mapDispatchToProps as second parameter
|
Released as 0.9.0, please verify. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you pass in more than one argument to
mapStateToPropsandmapDispatchToPropsthen we assume you are passing in props and so pass it in. Whenever the component receives new props we will re-invoke the function.Fixes #52