-
Notifications
You must be signed in to change notification settings - Fork 384
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: merge provider metadata on link account #1552
Merged
Merged
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
Pull Request Test Coverage Report for Build 8800052250Details
💛 - Coveralls |
kangmingtay
approved these changes
Apr 23, 2024
hf
pushed a commit
that referenced
this pull request
Apr 25, 2024
🤖 I have created a release *beep* *boop* --- ## [2.150.0](v2.149.0...v2.150.0) (2024-04-25) ### Features * add support for Azure CIAM login ([#1541](#1541)) ([1cb4f96](1cb4f96)) * add timeout middleware ([#1529](#1529)) ([f96ff31](f96ff31)) * allow for postgres and http functions on each extensibility point ([#1528](#1528)) ([348a1da](348a1da)) * merge provider metadata on link account ([#1552](#1552)) ([bd8b5c4](bd8b5c4)) * send over user in SendSMS Hook instead of UserID ([#1551](#1551)) ([d4d743c](d4d743c)) ### Bug Fixes * return error if session id does not exist ([#1538](#1538)) ([91e9eca](91e9eca)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
uxodb
pushed a commit
to uxodb/auth
that referenced
this pull request
Nov 13, 2024
It merges back the identity data into user metadata on link account. This is safe because the user can just sign-in again and have the identity data merged back (AccountExists case).
uxodb
pushed a commit
to uxodb/auth
that referenced
this pull request
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.150.0](supabase/auth@v2.149.0...v2.150.0) (2024-04-25) ### Features * add support for Azure CIAM login ([supabase#1541](supabase#1541)) ([1cb4f96](supabase@1cb4f96)) * add timeout middleware ([supabase#1529](supabase#1529)) ([f96ff31](supabase@f96ff31)) * allow for postgres and http functions on each extensibility point ([supabase#1528](supabase#1528)) ([348a1da](supabase@348a1da)) * merge provider metadata on link account ([supabase#1552](supabase#1552)) ([bd8b5c4](supabase@bd8b5c4)) * send over user in SendSMS Hook instead of UserID ([supabase#1551](supabase#1551)) ([d4d743c](supabase@d4d743c)) ### Bug Fixes * return error if session id does not exist ([supabase#1538](supabase#1538)) ([91e9eca](supabase@91e9eca)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 13, 2024
It merges back the identity data into user metadata on link account. This is safe because the user can just sign-in again and have the identity data merged back (AccountExists case).
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 13, 2024
🤖 I have created a release *beep* *boop* --- ## [2.150.0](supabase/auth@v2.149.0...v2.150.0) (2024-04-25) ### Features * add support for Azure CIAM login ([supabase#1541](supabase#1541)) ([1cb4f96](supabase@1cb4f96)) * add timeout middleware ([supabase#1529](supabase#1529)) ([f96ff31](supabase@f96ff31)) * allow for postgres and http functions on each extensibility point ([supabase#1528](supabase#1528)) ([348a1da](supabase@348a1da)) * merge provider metadata on link account ([supabase#1552](supabase#1552)) ([bd8b5c4](supabase@bd8b5c4)) * send over user in SendSMS Hook instead of UserID ([supabase#1551](supabase#1551)) ([d4d743c](supabase@d4d743c)) ### Bug Fixes * return error if session id does not exist ([supabase#1538](supabase#1538)) ([91e9eca](supabase@91e9eca)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 15, 2024
It merges back the identity data into user metadata on link account. This is safe because the user can just sign-in again and have the identity data merged back (AccountExists case).
LashaJini
pushed a commit
to LashaJini/auth
that referenced
this pull request
Nov 15, 2024
🤖 I have created a release *beep* *boop* --- ## [2.150.0](supabase/auth@v2.149.0...v2.150.0) (2024-04-25) ### Features * add support for Azure CIAM login ([supabase#1541](supabase#1541)) ([1cb4f96](supabase@1cb4f96)) * add timeout middleware ([supabase#1529](supabase#1529)) ([f96ff31](supabase@f96ff31)) * allow for postgres and http functions on each extensibility point ([supabase#1528](supabase#1528)) ([348a1da](supabase@348a1da)) * merge provider metadata on link account ([supabase#1552](supabase#1552)) ([bd8b5c4](supabase@bd8b5c4)) * send over user in SendSMS Hook instead of UserID ([supabase#1551](supabase#1551)) ([d4d743c](supabase@d4d743c)) ### Bug Fixes * return error if session id does not exist ([supabase#1538](supabase#1538)) ([91e9eca](supabase@91e9eca)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
It merges back the identity data into user metadata on link account. This is safe because the user can just sign-in again and have the identity data merged back (AccountExists case).