Replies: 1 comment 6 replies
-
We don't yet filter out getters, which is causing errors that lead to errors being thrown after loading so the values remain undefined. However, fixing that is going to increase the code size considerably, so it is not considered a use case that should be supported out of the box. To solve your issue, you should add your own serializer/deserializer that handles the data correctly. You can even fine-tune it to your use-case instead of relying on a bigger generic solution. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have this code in my project
DesktopNav.tsx
AuthStore.ts
but every time I get undefined from the storage, even when token is setted, probably because the data is not await yet. along with this, I don't get a reactive update when undefined already replaced with token.
I tried:
const isTokenSetted = () => Boolean(state.accessToken)
createResource(() => init)[0]();
I realize that I must somehow await for the value from the store, but I don't understand how.
Beta Was this translation helpful? Give feedback.
All reactions