20 ms·
This was exactly the motivation behind a project I wrote called react-redux-controller [1]. It has made for great separation of concerns between state managemen
by acjohnson55 9y ago
This was exactly the motivation behind a project I wrote called react-redux-controller [1]. It has made for great separation of concerns between state management (Redux), display logic (React), and implementation of processes (the controller functions). It's completely possible to segment portions of the app such that slices of those three aspects are colocated and then composed as needed.
I don't necessarily recommend using this project specifically, as I don't devote any time to maintaining it. There's a whole next-generation of how I think it should work that I haven't gotten around to persuing. But I mention it to back the overall approach. It makes UI refactors extremely easy, as components are generally not responsible for any dependencies of their descendant subtree, with the exception of some parent-child interactions.
I haven't tried it, but I think Freactal [2] also seems to allow for this sort of separation of concerns.
[1] https://github.com/artsy/react-redux-controller https://github.com/artsy/react-redux-controller
[2] https://github.com/FormidableLabs/freactal https://github.com/FormidableLabs/freactal