Redux Principles

  • Store is the Single source of truth
  • State is read-only
  • Mutations to the State are made with pure functions using Reducers
    • A reucer is like a property accessor (getter/settor), that sets the value of the property depending on the action, so if there is a boolean value in the store, called visibility, then the visibilityReducer will have a switch case for all the 20 different ACTIONS that it has to react to, and then will update the visibility property as per the logic.
  • Action is the representation of the change to the State
  • UI Should be a Pure Function of the Application State
  • Use Reducer Composition to maintain separation of concerns when updating State. For Eg. An ADD_TODO action is composed of Creating a new TODO item and adding it to TODO Array. These 2 things should be done by a different Reducers, the first which doesn’t need any state and simply returns new TODO object and the second reducer that actually adds this new TODO to the State.
  • The State of the App is formed by composing the states managed/returned by different reducers. This composition is managed by the Root Reducer
    • Eg. The State of ToDo App with Visibility Filters (ShowCompleted, ShowAll etc.) is formed by the root App reducer that returns the state created when the Action is passed to both todos reducer (further being composed of todo reducer) and the visibilityFilter Reducer that it comprises of:
    • Capture.JPG
    • This whole thing above can be replaced by helper function combineReducers() and the shorthand ES6 notation (if the reducer name and the state prop they manage have the same name):
    • Capture.JPG
    • Here “filter” is a property in the state that this action wants to set.
    • Capture.JPG
    • So basically the “SET_VISIBILITY_FILTER” Action is passed to both ToDos and VisibilityFilter reducer, which handle it separately, coz they manage different parts of the State:
      • VisibilityFilter reducer handles just the filter property of the Store and hence just updates that.
      • ToDos Reducer uses the payload to figure out if All ToDos are to be returned or just completed ones…
    • Q: If state’s ToDos array has been updated to have just completed tasks, then aren’t other tasks lost?
      • The Ans to this is key to local state vs Store State. Here, the visible todos are derived from all todos that come down from the Store.
      • This derivation happens locally in the container component, and is stored as local state, and is NEVER stored in the Store. In fact there isn’t even any action or reducer associated with this logic, coz it doesn’t touch the store at all.
    • Note that Actions need to be high level, for instance a TODO app with filters (Completed, All etc.) will have only these actions:
      • Add Todo
      • Toggle Todo
      • Filter Todos (Note that every filter is not an action in itself, instead,the filter type is passed in the payload of this action)





Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s