Details on persistState/storage

[strigefleur]

Documentation describes the way of using persistState to rehydrate the store from storage on page refresh (one way from storage to store I guess), though it's not obvious on backward operations. So there are some questions:

1. what is exactly the strategy on writing from store to storage? is it the only operation just before page refreshes or are there any extra triggers for it to happen?
2. what's the way to force the store to rehydrate itself from storage without calling for page refresh?

[NetanelBasal]

Each store update is saved to storage

[strigefleur]

Yup, guessed to check on sources finally.
Could you please provide some exported variant of loadFromStorageSubscription to call manually from the outside?

[HyruleGG]

What you try to do if I may ask? You can just work with the store without worrying about the localStorage at all

[strigefleur]

The original issue is in cross-tab sync whereas you have to publish/broadcast some data. So a quick draft many months ago led me to a BroadcastChannel browser API - a message-based browser tab interactions.

Imagine you have some state that persists to storage and rehydrates on tab refresh, then there are multiple tabs that may produce state data mutation you have to sync between all of the tabs. So you publish a message via BroadcastChannel on active tab, then other tabs probably receive it (unless unloaded or throttled by browser itself) and now the issue: you'd either need the whole state inside the message received or else you have to re-read the storage that actually have the recent data.

I believe the same exists already as Elf itself part here (had no chance to test it yet).