Raise an error for enablePersistence() in memory-only build #3128
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 fixes a regression in the memory-only build that went unnoticed because we never ran the memory-only integration tests on CI (see #3127).
We need to throw the right error if
enablePersistence()
is used in the memory-only build. If it is used, the "durable" flag will be true in the MemoryComponentProvider, which should trigger a user-level exception and not a debugAssert.