Recipe: State Reducer Event Listener #14
Description
Demonstrate how multiple reducers can be passed into a single state reducer to decouple complexity in the actions. A good example would be to use a
- analytics reducer
- error logging reducer
- state reducer
An api call for pokemon and then the context will handle each scenario it's own way.
It would be nice to do a diagram and explain why this pattern is nice as it decouples business / UI / observability logic from each other.
Talk about alternatives and how redux does this with listeners in slices.