This pull request introduces changes to the VerificationForm component to support token-based verification, replacing the previous email-based verification method.
Changes:
Added email field to the VerificationStatusResponse interface.
Updated useEffect to extract the token from URL parameters instead of email.
Modified the checkVerificationStatus function to accept a token as an argument instead of email.
Updated the API call within checkVerificationStatus to use the token parameter.
Set the email state in the component based on the response from the API.
Adjusted the success message logic to align with the new token-based verification process.
Purpose:
The purpose of this pull request is to enhance the security and consistency of the verification process by utilizing a unique token instead of an email address. This change ensures a more secure and standardized approach to user verification.
Description:
This pull request introduces changes to the
VerificationFormcomponent to support token-based verification, replacing the previous email-based verification method.Changes:
emailfield to theVerificationStatusResponseinterface.useEffectto extract thetokenfrom URL parameters instead ofemail.checkVerificationStatusfunction to accept atokenas an argument instead ofemail.checkVerificationStatusto use thetokenparameter.emailstate in the component based on the response from the API.Purpose:
The purpose of this pull request is to enhance the security and consistency of the verification process by utilizing a unique token instead of an email address. This change ensures a more secure and standardized approach to user verification.
This pull request fixes (#11)