fix get_user calls fail when no session or jwt is available #315
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?
Fix #314
What is the current behavior?
Currently an error is returning from supabase request
What is the new behavior?
My update short circuits to prevent the supabase request from being made if there is no jwt and no session
Additional context
This mostly follows the logic of the get_session calls
Since it may not be obvious, my use case is a server side auth handler. Flow is as follows
Flask route info causing the break: