Skip to content
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

Documents with emailConfirmed: false and a non-null emailConfirmedAt #208

Open
AlbertoPdRF opened this issue Jul 27, 2020 · 2 comments
Open
Labels
bug Something isn't working full stack Requires work on both the front and back ends of the application

Comments

@AlbertoPdRF
Copy link
Owner

Describe the bug
There are some documents on the database with a non-null emailConfirmedAt attribute but with emailConfirmed: false.

To Reproduce
Not sure why it happens, it needs to be investigated.

Expected behavior
If the email is not confirmed (i.e. if emailConfirmed: false), emailConfirmedAt must be null.

@AlbertoPdRF AlbertoPdRF added the bug Something isn't working label Jul 27, 2020
@AlbertoPdRF AlbertoPdRF added the full stack Requires work on both the front and back ends of the application label Sep 11, 2020
@idiglove
Copy link
Contributor

I don't think it's possible for emailConfirmedAt to be null as it is described in Schema
emailConfirmedAt: { type: Date },

@AlbertoPdRF
Copy link
Owner Author

Actually, emailConfirmedAt is never null per se, but unless a user's email is confirmed, it isn't present on the corresponding document. The bug here is that there are users with an emailConfirmedAt value that have an emailConfirmed value of false, which shouldn't happen.

If you'd like to dig deeper into this, let me know and I'll assign the issue to you! 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working full stack Requires work on both the front and back ends of the application
Projects
None yet
Development

No branches or pull requests

2 participants