Skip to content
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

Suisin/upm826/success modal phone number verification #89

Conversation

suisin-deriv
Copy link
Owner

Changes:

Add success modal for phone number verification

Screenshots:

Screenshot 2024-05-09 at 6 11 14 PM

@@ -744,6 +744,8 @@ type TUiStore = {
setRealAccountSignupEnd: (status: boolean) => void;
setPurchaseState: (index: number) => void;
simple_duration_unit: string;
should_show_phone_number_verified_modal: boolean;
Copy link
Collaborator

@amina-deriv amina-deriv May 9, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need this observer ?

This modal will be triggered only when phone number otp is verified. Isnt?
Can we just trigger the modal on success on API call then?

Copy link
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeap but the modal will be displayed on personal-details-page, so when we check for verified: 1 api call this modal will show up everytime isn't 🤔 I was thinking that when user clicks on verify button, when the API call isSuccess then we put the value in store and redirect user back to personal details then dispaly the successful modal

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lets check with design team on this flow

@suisin-deriv suisin-deriv merged commit 43cb445 into suisin/utkarsha/UPM819/phone_verification_flow May 13, 2024
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants