fix: add verify argument to _init_supabase_auth_client()
#913
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
grdsdev
changed the title
verify argument to _init_supabase_auth_client()verify argument to _init_supabase_auth_client()
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Add
verifyargument to_init_supabase_auth_client()for SSL certificate verification. This follows the convention set by_init_postgrest_client()and_init_storage_client().What is the current behavior?
verifyflag cannot be passed to the underlying[Async]GoTrueClient.What is the new behavior?
_init_supabase_auth_client()can be passed theverifyflag that is propagated to the underlying[Async]GoTrueClient.Additional context
Follows convention of #813