Added GetUser method that supports a JWT. #39
Merged
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 a GetUser method with a JWT parameter. Using this to verify a user on a back end service.
Reasoning for adding it is based on this issue: supabase/supabase#147
Whereas you can do this in javascript:
What is the current behavior?
Currently the API is not exposing the method to fetch user data using a JWT.
I've added this method so it is exposed to the client. So it can be used on backend services to validate JWT's.
What is the new behavior?
Method in Client that allows you to fetch the user using GetUser(jwt).
Called like so:
Additional context
No further context. Feel free to ask questions or explain to me a better way to solve my problem if there is any.