Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Don't Override Name Upon Repeat # #76

Open
billdybas opened this issue Feb 17, 2018 · 0 comments
Open

Don't Override Name Upon Repeat # #76

billdybas opened this issue Feb 17, 2018 · 0 comments

Comments

@billdybas
Copy link
Member

There are two ways a user can be created:

  1. They #to the system
  2. They are created through the "UserForm" on the frontend, usually through scoreboard

Every time someone signs into the system w/ Google, we override their first and last name to what Google provides, therefore, we can't technically update a user's name (or build me v2) because it will just revert the next time they log in.

I think in our login flow, if the user already has a first and last name, we shouldn't update it. This would allow us to actually build another me as well as member management pages for officers.

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

No branches or pull requests

1 participant