Migrating from pinia-plugin-persistedstate-2 about pinia-plugin-persistedstate HOT 6 CLOSED

The plugin only supports synchronous storages to match pinia's mutation system. This is indeed one of the limitation.

from pinia-plugin-persistedstate.

The plugin only supports synchronous storages to match pinia's mutation system. This is indeed one of the limitation.

Can you suggest a migration path for users coming from the abandoned -2 version then?

from pinia-plugin-persistedstate.

Well I didnt make the -2.

This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214).
You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

from pinia-plugin-persistedstate.

Well I didnt make the -2.

This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214). You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

Oh yeah, I'm aware, I was just wondering if you have a suggestion for a replacement path, I'll look at actions but that looked like I have to have those defined for every store instead of globally, thanks!

from pinia-plugin-persistedstate.

Well I didnt make the -2.
This plugin has only ever officially supported synchronous storages as mentioned in several issues (#17 #111 #214). You can use pinia actions for this, or the hooks, or still use non-awaited functions in the storage, but may experience side effects.

Oh yeah, I'm aware, I was just wondering if you have a suggestion for a replacement path, I'll look at actions but that looked like I have to have those defined for every store instead of globally, thanks!

Would be cool if you could do something like this:

pinia.use(
    createPersistedState({
      actions: {
        getItem: async (key) => {
          return getStore(key);
        },
        setItem: async (key, value) => {
          return setStore(key, value);
        },
        removeItem: async (key) => {
          return deleteStore(key);
        },
      },
    }),
  );

from pinia-plugin-persistedstate.

Due to the way the plugin behaves and how pinia handles it, synchronozing data from async sources is out of the scope of the plugin. My advice would be to have calls done on app startup then calling stores to update the data. That would be the safest way without risking race conditions having async calls in sync functions.

Closing this 😌

from pinia-plugin-persistedstate.