fix(auth): add providers type to UserAppMetadata interface #1760
Conversation
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
3 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.
Moved from supabase/auth-js#1011
Author: @j4w8n
What kind of change does this PR introduce?
Minor type fix.
What is the current behavior?
If a user has multiple providers associated with them, then Supabase adds a
providersstring array to theiruser.app_metadata, but this is missing from theUserAppMetadatatype. I just happened to notice this while trying to work around an issue in a demo app, and there was noprovidersintellisense in my IDE.What is the new behavior?
A
providers?: string[]type is added to the interface.Additional context
An example of multiple providers being associated to a user is if the user signs up with email/password, but then is allowed to add a phone number as well.