Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • @StevenBayer did i miss something important? Commented Jun 23, 2016 at 1:08
  • 1
    With De-composing my reducers I still end up with complex objects they are just slightly less nested. Nothing important missed, just a helpful link incase someone else googles this issue. Commented Jun 23, 2016 at 1:12
  • 3
    @StevenBayer your state tree will remain the same. But at each reducer, you will be dealing with simpler data structure. Sorry I wasn't clear in the post. Also, you don't always need combineReducer. Reducers are just functions that takes state and action as parameters. You can call another reducer function in a reducer function to reduce the responsibilities of each reducer. Commented Jun 23, 2016 at 1:18
  • 1
    I'm not sure how I would implement a sub-reducer on state.roomLists or even more so for state.roomLists[n].listItems[n]. Also wouldn't the sun functionality of the sub-reducers add up to a deep clone? Commented Jun 23, 2016 at 1:41