Note on Redux - revaturelabs/revoverflow-frontend GitHub Wiki

Currently the values tracked by the Redux store remain persisted through browser refreshes by storing question id values, question objects, and answer objects in local storage when a question is clicked from the feed. These key values and objects are retrieved from storage when needed, and are primarily used in sending a request to an endpoint made available by revoverflow-backend. Not all states are stored within the Redux centralized store. In general, if a state only belongs to a single component, and in some cases that component's children, that state is not tracked within the Redux store. It was the original goal of the revoverflow-frontend team to have all states stored within the Redux store, unless only and strictly existing within a single component. While the future decisions of where to maintain states should be considered on a case to case basis, we suggest placing them within the state store unless one of two circumstances are encountered: the only and strictly belongs to a single component, or there is significant advantage in having the state maintained within the component.