fallback to default version in migrations #546
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related issue/comment: #434 (comment)
What's changed?
Currently if you try and upgrade from v4 to v5 using https://github.com/rt2zz/redux-persist/tree/b85b56a889ebd4919c9ba11d239a4ae1861e1da6#experimental-v4-to-v5-state-migration and also add a migration, the migration will attempt to run on the v4 state which has no
_persist
version.This pr would allow the migration to fall back on the default version in such a scenario.
Considerations
_persist.version
._persist
in the v4getStoredState
so the v4 migration will not affect any other parts of the code?