@wcjohnson did some initial playing around with redux-components using the redux todos example. I converted the todos reducer/actions into a redux component. Took me a little while to get my head around the difference between the todos component and the todos state. I believe I'm right in saying that you need to come up with a way to pass the redux component to interested things in the view code because it's no longer sufficient to just import actions. You need to call the actions methods on the associated component. So for my experiment I passed the redux component in as a prop to the App and the App component passed it on to the AddTodo and the VisibleTodoList. Does that sound like the right approach?
I guess maybe when you fully embrace the component model, your connected view components stop interacting with the redux store state object directly, and instead get all the state from the redux components they interact with?
createComponent) and the singletons can be separately
required by the views that need them.
Observableresulting form that selector
recomposeto build React components, and I have a higher order helper function
withReduxComponentsthat basically takes an object describing the binding you want with state code and makes it happen. I will ask the higher ups about open sourcing it this week, I'm fairly sure they will allow it