Demonstrate koConnect to piggyback on identical mapStateToProps, etc. #13
Conversation
| @@ -21,3 +21,5 @@ export default function configureStore(initialState) { | |||
|
|
|||
| return store | |||
| } | |||
|
|
|||
| export default configureStore(); | |||
There was a problem hiding this comment.
what's the purpose of exporting the called configureStore function here rather than just calling it where it's imported?
There was a problem hiding this comment.
For the KO example, the call to koConnect needed access to the store because there wasn't a top-level <Provider> component passing it around in context.
So, the call to koConnect either needed to be in the same file that configureStore() is called in (i.e. index.js previously), or we needed to put the result of calling configureStore in a place that was importable in multiple files (in this case, index.js and components/Email.js).
If we were actually building a Knockout-Redux app, we could probably do something like <Provider> and pass around a context to child view models like react-redux does, but for purposes of this example, it wasn't really important.
No description provided.