feat: exposing keyName to SupabaseContext#22
Merged
Conversation
- Only passing keyName for during 'createContextClient' if the authType is public
tomaspozo
approved these changes
Apr 1, 2026
Member
tomaspozo
left a comment
tomaspozo
left a comment
There was a problem hiding this comment.
This is a great addition! and fix too :)
This was referenced Apr 1, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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?
Bug fix, feature, docs update
What is the current behavior?
SupabaseContextdoesn't have theauth.keyNamewhich would be useful for some cases.secret:keythere's a bug which requires this key to be defined atpublishableKeysenvironment prop.What is the new behavior?
authKeyNameproperty toSupabaseContextauthTypeverification before passing down thekeyNamewhile creating the supabase client