Skip to content

Expose email on reset-password-email screen data#329

Merged
amitsingh05667 merged 1 commit intoauth0:masterfrom
v-nemeth:fix/expose_email_value_on_reset_password_email_screen
Mar 9, 2026
Merged

Expose email on reset-password-email screen data#329
amitsingh05667 merged 1 commit intoauth0:masterfrom
v-nemeth:fix/expose_email_value_on_reset_password_email_screen

Conversation

@v-nemeth
Copy link
Contributor

@v-nemeth v-nemeth commented Mar 4, 2026

Description

This PR exposes the email field on the reset-password-email screen so it is accessible to frontend consumers via useScreen().data.email.

After submitting an email on the reset-password-request screen, the server correctly returns the submitted email address in the screenContext.data for the subsequent reset-password-email screen. However, this value was not accessible from the frontend SDK because:

  • reset-password-email/screen-override did not explicitly map the email field into the screen data. (it did this implicitly)
  • The ScreenMembersOnResetPasswordEmail interface did not expose email, preventing TypeScript consumers from referencing it.

In practice, username is often unset for this screen, while email contains the relevant value needed to render confirmation UI (e.g. “We sent an email to…”).

Changes

  • Expose email in ScreenMembersOnResetPasswordEmail and ScreenDataOptions
  • Map email from screenContext.data in the reset-password-email screen override

This brings the frontend SDK in line with the data already provided by the server and matches developer expectations.

Impact

  • No breaking changes
  • Enables access to existing server-provided data
  • Improves developer experience when building custom UIs for password reset flows

References

Related issue:

Testing

  • Manually verified by submitting an email on the reset-password-request screen and accessing useScreen().data.email on the reset-password-email screen.
  • No existing tests were modified; this change only exposes already-available data.

Environment

@auth0/auth0-acul-react: 1.0.0
Browser: Chrome

Checklist

  • I have added documentation for new/changed functionality in this PR or in auth0.com/docs
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used, if not the default branch

@v-nemeth v-nemeth marked this pull request as ready for review March 4, 2026 08:29
@v-nemeth v-nemeth requested a review from a team as a code owner March 4, 2026 08:29
@amitsingh05667 amitsingh05667 merged commit 27c8d6e into auth0:master Mar 9, 2026
1 check passed
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