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
Describe any alternatives/workarounds you're currently using
Other information:
If accepted, I would be willing to submit a PR for this feature
[ ] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No
Currently, when store-devtools is enabled and feature stores are loaded, it uses the same @ngrx/store/update-reducers action to recompute the state history. This is confusing because users think its changing state, when its just a pass-through action to update the reducer map. Update this to a new action that is more descriptive and accurate of what's happening.
The text was updated successfully, but these errors were encountered:
// Recompute state history with latest reducer and update actioncomputedStates=computedStates.map(cmp=>({
...cmp,state: reducer(cmp.state,liftedAction),}));
Is this a case of replacing liftedAction with RECOMPUTE_STATE_ACTION?
Describe any alternatives/workarounds you're currently using
Other information:
If accepted, I would be willing to submit a PR for this feature
[ ] Yes (Assistance is provided if you need help submitting a pull request)
[ ] No
Currently, when store-devtools is enabled and feature stores are loaded, it uses the same
@ngrx/store/update-reducers
action to recompute the state history. This is confusing because users think its changing state, when its just a pass-through action to update the reducer map. Update this to a new action that is more descriptive and accurate of what's happening.The text was updated successfully, but these errors were encountered: