-
Notifications
You must be signed in to change notification settings - Fork 223
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
Handling unconfirmed emails #74
Comments
@vinnicc I believe the commented line came from the original schema I took from Devise. I have not looked into how that field is used. If you would like to outline the use case here, I'll review and get back to you on recommendations. Steve |
Pretty much the same as Devise - when the user's first email has been confirmed and then updated to a different one, the new email could be temporarily stored in This will be useful for the front end and to prevent the app from unintentionally blocking the user in some cases. I just thought this completes the "confirmable" behavior and you might want it included in the library. |
@vinnicc @smpallen99 maybe we can close this issue ? |
What would be the recommended way to handle subsequent unconfirmed emails?
Coherence.Schema
has this line commented out so I wonder if there's a plan to add this feature soon (like how Devise does it, without support for multiple emails though).The text was updated successfully, but these errors were encountered: