fix: Use return instead of throwing a duplicate email error. #166
Conversation
|
Hi! I'm VTEX IO CI/CD Bot and I'll be helping you to publish your app! 🤖 Please select which version do you want to release:
And then you just need to merge your PR when you are ready! There is no need to create a release commit/tag.
|
|
Beep boop 🤖 I noticed you didn't make any changes at the
In order to keep track, I'll create an issue if you decide now is not a good time
|
Rudge
force-pushed
the
hotfix/B2BTEAM-1906-change-throw-to-return-duplicated-email
branch
from
1a397db to
459e5a1
Compare
|
Rudge
deleted the
hotfix/B2BTEAM-1906-change-throw-to-return-duplicated-email
branch
|
Your PR has been merged! App is being published. 🚀 After the publishing process has been completed (check #vtex-io-releases) and doing A/B tests with the new version, you can deploy your release by running:
After that your app will be updated on all accounts. For more information on the deployment process check the docs. 📖 |
What problem is this solving?
We found a lot of error logs when the user already exists and someone tries to add the same email.
So, we removed the throwing to avoid excessive logs of errors treated.
How should this be manually tested?
Try to add an existing email user to the Buyer organization.
Screenshots or example usage:
