We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@nuxtjs/supabase: 1.5.0 nuxt: 3.16.1
To follow if requested.
Client will not have user value because the session/token is now invalid.
Client has user value.
The server plugin uses getSession() and getUser() from the sdk.
getSession()
getUser()
The client plugin relies on getSession() which according to the Supabase docs is not recommended.
Regardless it's still not the same as server because server uses getUser() for the user.
I might even add not to populate it manually on client side and just handle the updates.
useState() should already share state from server to client.
useState()
the server plugin already had it done correctly.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Version
@nuxtjs/supabase: 1.5.0
nuxt: 3.16.1
Reproduction Link
To follow if requested.
Steps to reproduce
What is Expected?
Client will not have user value because the session/token is now invalid.
What is actually happening?
Client has user value.
The server plugin uses
getSession()
andgetUser()
from the sdk.The client plugin relies on
getSession()
which according to the Supabase docs is not recommended.Regardless it's still not the same as server because server uses
getUser()
for the user.I might even add not to populate it manually on client side and just handle the updates.
useState()
should already share state from server to client.the server plugin already had it done correctly.
The text was updated successfully, but these errors were encountered: