feat(email-verification): add EMAIL_UPDATE support to resend flow#20187
feat(email-verification): add EMAIL_UPDATE support to resend flow#20187ratishjain12 wants to merge 11 commits intotwentyhq:mainfrom
Conversation
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
ratishjain12
force-pushed
the
feat/email-update-resend-trigger
branch
from
d05b2c1 to
bdabaea
Compare
ratishjain12
force-pushed
the
feat/email-update-resend-trigger
branch
from
ce7c1ad to
3aee665
Compare
📊 API Changes ReportGraphQL Schema ChangesGraphQL Schema Changes[error] Error: Unable to read JSON file: /home/runner/work/twenty/twenty/main-schema-introspection.json: Not valid JSON content GraphQL Metadata Schema ChangesGraphQL Metadata Schema Changes[error] Error: Unable to read JSON file: /home/runner/work/twenty/twenty/main-metadata-schema-introspection.json: Not valid JSON content REST API Analysis ErrorError OutputREST Metadata API Analysis ErrorError Output |
…erificationTrigger enum
…e resendEmailVerificationTokenArgs
…icationToken mutation
…ire verificationTrigger parameter
ratishjain12
force-pushed
the
feat/email-update-resend-trigger
branch
from
040edc1 to
6809c50
Compare
…ailVerificationToken function
3 participants
fixes #20186
Problem
The resendEmailVerificationToken method hardcodes EmailVerificationTrigger.SIGN_UP when calling sendVerificationEmail().
While sendVerificationEmail already supports both SIGN_UP and EMAIL_UPDATE triggers (with different email subjects), the resend flow cannot differentiate between a signup verification resend and an email update verification resend.
Impact: When a user updates their email and requests a resend, they receive "Welcome to Twenty: Please Confirm Your Email" instead of "Please confirm your updated email" — incorrect branding and user confusion.
Solution