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
BREAKING CHANGE: add forgot password feature in the SupaEmailAuth widget #46
Conversation
Proposed
Breaking: add forgot password feature in the SupaEmailAuth widget
@FatumaA @Csierram96 |
Will do additional cleanup of example directory if we think this PR is a good idea. |
Seems like the next logical step 🙂. I will take a closer look a little later today. Thank you for continuing to maintain this while I could not! |
I'll also take a look by eod. But by looking at the description and the video looks like a nice change/feature |
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.
I think switching the '/' from SignIn to home is not necessary since it is an auth lib. I'm assuming that the sign in screen is what should be at the root?
If we keep that change we have to make minor changes on how the app switches screen
Otherwise it looks fine 👍🏽
I will add a commit to remove the forgot password text as it shows doubly
also, do we still need the update_password screen in the example?
I have noticed a bug on validation: fields stay in error even when you toggle between the screens in supaEmailAuth
Remove the forgot password and don't have account text buttons from the example
/// | ||
/// Typically used to pass a DeepLink | ||
final String? redirectUrl; | ||
/// If email confirmation is turned on, the user is |
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.
Maybe I'm reading this wrong, but I dont get this description. The user is
, is there something missing here?
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 is very much a typo! Thanks for finding it, and I will fix it!
MapEntry(metaDataField.key, controller.text)), | ||
); | ||
) | ||
: Text(_isSigningIn ? 'Sign In' : 'Sign Up'), |
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.
not related to this PR but would be nice to be able to modify the text that shows up. This would be useful to handle intl
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.
Yup, for sure! Certainly something we would want to do in the near future!
It looks like a really good addition. Just curious, what are the cons that you see of adding this? |
Thanks for all the positive comments!
Thanks for the feedback! Makes sense! Will put it back the way it used to be!
Yup, I haven't actually checked the example app thoroughly yet. I just wanted to show this feature to you to get some feedback! I will do some cleanup of the example directory! |
Thanks for the positive feedback @Csierram96 !
I guess I had two things:
|
That makes sense. The braking change should be fine as you mentioned as this has not been released as stable. And regarding the flexibility that's actually a good point. Personally I prefer something that just works out of the box for this kinda stuff (firebase ui or supabase ui). And if you want more flexibility you can implement your own UI. |
Thanks @Csierram96 for the nice comment! It's nice to receive a sanity check from other developers! I will do some additional clean up on this PR and merge it in! |
Proposed
Breaking: add forgot password feature in the SupaEmailAuth widget
I think this one is good to be reviewed! |
What kind of change does this PR introduce?
This PR combines the forgot email flow, signIn, and signUp into a single widget so that the developer using this library does not have to separately implement it.
The aim for this PR is to make it more similar to how Supabase auth UI for react is implemented.
This PR adds the following
authAction
parameter onSupaEmailAuth
widget.SupaEmailAuth
widget, so that there is no need for developers to have two separateSupaEmailAuth
in two different places.With this PR, you can have this code
To get this: