Storage and Schema Migration Combo Test #6690
Open
+525
−238
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.
This PR contains:
A failing test that incorporates both storage migration and schema migration.
Describe the problem you have without this PR
Updating schema in between storage migrations without updating the version numbers is currently allowed behavior.
Then, when trying to then implement a normal schema migration strategy afterwards, the migration strategy starts throwing error unknown migration error, DM4.
I tried to see if
getOldCollectionsMeta()
was potentially causing this, but it wasn't returning anything in this context.Todos