This Pull Request is intended to correct the bug that allows users to use an invalid email(non-existing domain part) for registration, login, request-magic-link, and reset-password.
Description
This Pull Request is intended to correct the bug that allows users to use an invalid email(non-existing domain part) for registration, login, request-magic-link, and reset-password.
Prior to this PR, users were able to register, login with an invalid email like johnson.pragui@gmail.com.com or johnson.oragui@example.com, but with this fix, the email validation on these four endpoints mentioned above are now properly validated.
This Pull Request is intended to correct the bug that allows users to use an invalid email(non-existing domain part) for registration, login, request-magic-link, and reset-password.
Description
This Pull Request is intended to correct the bug that allows users to use an invalid email(non-existing domain part) for registration, login, request-magic-link, and reset-password. Prior to this PR, users were able to register, login with an invalid email like johnson.pragui@gmail.com.com or johnson.oragui@example.com, but with this fix, the email validation on these four endpoints mentioned above are now properly validated.
Related Issue (Link to issue ticket)
Invalid email on login
Invalid email on registration
invalid email on password reset
invalid email on magic-link
Motivation and Context
How Has This Been Tested?
This has been tested with pytest and postman.
Screenshots (if appropriate - Postman, etc):
Types of changes
Checklist: