Restrict OTP Sending to Valid Emails Only (#23) #31
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
@inv-amalusudhakaran is attempting to deploy a commit to the Sailing SAM's projects Team on Vercel. A member of the Team first needs to authorize it. |
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.
#23
This PR addresses an issue where users could request OTP for invalid email addresses (emails not ending with @sst.scaler.com or @scaler.com). The following changes have been implemented:
Introduced validation logic to ensure that the "Send OTP" button is enabled only when the entered email matches the required domains.
Updated the handleEmailChange function to validate the email and set the button's state accordingly.
Prevented OTP requests for invalid emails by disabling the button or hiding it when the email is invalid.