History is currently saved as an array in the timeReducer. It makes sense to separate out the history into it's own reducer. This should make data resets cleaner. Especially when timers get added and have their own history.
This will have an affect on how data is stored to local storage since we will need to either save multiple keys in local storage or build the data from multiple reducers on each save. Investigation is required.
History is currently saved as an array in the timeReducer. It makes sense to separate out the history into it's own reducer. This should make data resets cleaner. Especially when timers get added and have their own history.
This will have an affect on how data is stored to local storage since we will need to either save multiple keys in local storage or build the data from multiple reducers on each save. Investigation is required.