You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in persisting the cached data and sharing it across tabs (e.g. via broadcast). This opens up the possibility of a client writing data in one schema and another client (in a different tab or in the future) expecting another schema.
I would like to be able to parse the cached entry before returning and potentially busting the cache key if it is invalid, or migrating it on the spot.
Looking at the docs I haven't found a way to achieve this, but I might have missed something.
If it is not possible currently, is this something that would have a place in the library and is it practical to implement?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm interested in persisting the cached data and sharing it across tabs (e.g. via broadcast). This opens up the possibility of a client writing data in one schema and another client (in a different tab or in the future) expecting another schema.
I would like to be able to parse the cached entry before returning and potentially busting the cache key if it is invalid, or migrating it on the spot.
Looking at the docs I haven't found a way to achieve this, but I might have missed something.
If it is not possible currently, is this something that would have a place in the library and is it practical to implement?
Beta Was this translation helpful? Give feedback.
All reactions