Redux Middleware To Think About

Too Long; Didn't Read

When working in <a href="https://hackernoon.com/tagged/redux" target="_blank">redux</a> recently, my team and I found ourselves writing a lot of unnecessary logic in functions to keep certain leaves of state from firing off because one listener was triggered. By writing a lot of this logic several ideas arose as how we could move some of the logic out of my functions that triggered reducers, and be more <a href="https://hackernoon.com/tagged/dynamic" target="_blank">dynamic</a>. In doing so we thought of the idea of adding methods to redux that handled certain actions and overall gave me more control over the state object. Some challenges we faced were; distinguishing between keys in a deeply nested state object, intercepting dispatched actions before making changes to state, and making tradeoffs between space and time complexity, something we are still going back to and evaluating.