fix: insert all available user information at creation time #802
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
bolmsten
approved these changes
Oct 2, 2024
deepaksftc
approved these changes
Oct 2, 2024
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.
Description
Some user attributes are only updated after the second login of the user (first login will create the user in the users table, the second login will update the existing record).
Motivation and Context
It is confusing that some user attributes will only be set after the second login.
How Has This Been Tested
Manual testing + e2e.
Fixes
Synchronize the inserted / updated user attributes.
Changes
Update upsert method in OAuthAuthorization.ts.
Depends on
N/A
Tests included/Docs Updated?