Update supa_email_auth.dart: Added email to the Password reset email sent callback #146
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…sent callback The email was not accessible inside the callback, and was needed to implement OTP token verification in the app itself, instead of the password reset link flow.
|
Kindly review this merge request |
Added an optional initialEmail to pass in a saved email address so that the email field is already populated. Passed in the email to the onSignInComplete() callback, so that the email can be used inside (eg. for saving to sharedPreferences) Also, added a focus node for the password field to move the focus to it if the initialEmail is non-empty.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The email for which the password reset is requested was not accessible inside the callback, and was needed to implement OTP token verification in the app itself, instead of the password reset link flow.
What kind of change does this PR introduce?
Feature: It enables OTP verification through email
What is the current behavior?
OTP verification is currently not possible because the email is necessary to ensure that the OTP entered belongs to the same email that requested the password reset.
What is the new behavior?
The email for the user is accessible in the callback and can be inserted into the Supabase.instance.client.auth.verifyOTP() function.