-
Notifications
You must be signed in to change notification settings - Fork 9
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
Bug - Improve unique email validation #4103
Conversation
What bug does this fix? How do we test it? |
https://talent-cloud.slack.com/archives/C0259G6KXJ6/p1664382823644029 |
Sorry @petertgiles . I was in such a rush to get this up I forgot to write a proper description with testing instructions. Essentially, when we added the unique email rule for |
Oh no! That's what I get for ignoring Cypress I guess. 🤦 Thanks for fixing this so quickly. |
Felt responsible since I approved it. I don't like that cypress is being marked as "skipped" rather than "failed" right now. |
@petertgiles Sorry, I did not realize the massive diff for gc-digital-talent/api/graphql/schema.graphql Lines 975 to 977 in b0bbd90
gc-digital-talent/api/graphql/schema.graphql Lines 1042 to 1044 in b0bbd90
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice job! This fixes the error for me. Two small things to check on.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you got it! 🏅
Summary
This resolves an issue with not being able to update an existing user due to the unique email validation by ignoring the user you are updating.
Testing
npm run codegen --workspaces
npm run production --workspaces
/admin/users/
/talent/profile