feat: add async getters for session and user. #265
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
adds async getters for session and user.
this provides a workaround for #143 and #23 without needing setTimeout.
this is an alternate solution to #147.
What is the current behavior?
After
const supabase = createClient(supabaseUrl, supabaseKey)
supabase.auth.session()
andsupabase.auth.user()
might returnnull
,if the session is expired and currently refreshing or if the session is recovering from a magic link.
What is the new behavior?
refreshedSession()
resp.refreshedUser()
wait for the pending recovery andand return valid
session
resp.user
data.usage examples
Additional context
for supabase-js v2 (supabase/supabase-js#170)
user() and session() should IMHO be async functions.