You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you invoke store.replaceReducer(newReducer) the last 50 (maxage default param) actions are applied/run-through the store.
This has the potential to break a lot of applications, mine in particular where several of the last 50 actions are using http or socket middleware for async actions. During the state of my application I use code-splitting which involved heavy utilization of store.replaceReducer anytime a new module is loaded I register a new reducer dynamically thus invocation of replaceReducer.
Is this intended to be a feature or a potential bug? Thanks!
The text was updated successfully, but these errors were encountered:
When you use store.replaceReducer the effect will be the same as for hot-reloading, where the extension is recomputing all the history again. To avoid that set shouldHotReload parameter to false.
When you invoke
store.replaceReducer(newReducer)
the last 50 (maxage
default param) actions are applied/run-through the store.This has the potential to break a lot of applications, mine in particular where several of the last 50 actions are using http or socket middleware for async actions. During the state of my application I use code-splitting which involved heavy utilization of
store.replaceReducer
anytime a new module is loaded I register a new reducer dynamically thus invocation ofreplaceReducer
.Is this intended to be a feature or a potential bug? Thanks!
The text was updated successfully, but these errors were encountered: