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
I'm using paths to store pieces of my state. The paths I specify don't influence the initial state, they only affect what's stored after the state changes.
I'd expect my store to only to get paths from redux localStorage that I specify when creating the store
I'm using
paths
to store pieces of my state. The paths I specify don't influence the initial state, they only affect what's stored after the state changes.I'd expect my store to only to get paths from redux localStorage that I specify when creating the store
On page one, I use path "A"
On page two, I use path "B"
If I first land on page one, and then go to page two, "A" will be in my state even though it's not in my paths.
When I leave page two, "A" will be removed, and "B" will persist, but I was expecting to not get "A" on page two at all
If the slicer was applied to
persistedState
in this persistState.js, it'd fix this issue:I could submit a PR if you're merging those :) Or if this was done intentionally, lmk
The text was updated successfully, but these errors were encountered: