Computed properties with a runtime argument missing when used with persistence?

With persistence turned on our app throws Error in useStoreState: state.assets.getStakedAssetsByAddress is not a function..

It is a computed property with a runtime argument.

getStakedAssetsByAddress: computed(
  (state) => (address) => Object.values(state.stakedAssetsById[address]) || []
),

This exact issue was tackled in v4. https://github.com/ctrlplusb/easy-peasy/issues/503 Could there be a regression in v5?

[ctrlplusb]

Thanks for taking the time to put this together for me.

[GollyJer]

OK. I’m back with the example @ctrlplusb.

Here’s the snack. easy-peasy-persist-computed-bug

I set the store up the same way we do our production app. You will notice we build a pretty complex import structure for the store, but it’s easier to manage in the long run.

• Pick the Android emulator.
• When you initially load the app, with nothing persisted, it works great.
• Then comment lines 15-23 and uncomment lines 25 - 33, hit the Save button at the top right, and reload the app.
• You will get state.thing1.getAllTheThings is not a function.
• Now, pick the iOS emulator.
• App will load fine the first time.
• Click Devices > Reload Apps at the bottom right menu of snack.
• You will get state.thing1.getAllTheThings is not a function.
• I think this has something to do with persistence because there isn’t persisted state when the app initially loads (no error), but there is from that point forward (with error).

And if you’re wondering why I’m not using Easy Peasy’s persistence. 👉 https://github.com/ctrlplusb/easy-peasy/issues/672 Maybe related?