-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
fix: email update #2158
fix: email update #2158
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks OK, just wondering if zod will break when secure site starts returning new data and old versions can't handle it.
Did you try new secure site with older versions of w3m?
@tomiir yes, i tested the new secure site with an old version of w3m and it doesn't break because Log using old w3m and new secure-site -> zod filters the new payload in
|
@arein @lukaisailovic added update email tests |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
New change has been merged in V4
that uses random emails for each tests. Refer to that and update so we use that approach for this test as well
Changes
updateEmail
response to decide whether to redirect to first or second OTP screenSteps to reproduce issue in production:
Associated Issues
https://linear.app/walletconnect/issue/W3M-171/%5Bbug%5D-freeze-update-email-flow-when-otp-is-sent-to-new-email-only
Related
Secure site PR 120