Interactivity API: Fix state intialization for asynchronous private stores #58754
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.
What?
Fixes a bug that appears when a private store is loaded asynchronously, and the page contains the initial state for that store.
Why?
The current implementation makes those stores become public, thus making private stores throw an error when they try to lock their namespace.
How?
Using the
universalUnlock
variable defined instore.ts
. That prevents the store from being marked as "public" and can be set as "private" later on.