Skip to content

Conversation

@LilyFirefly
Copy link

The variable User.email_verification_required is named based upon the presumption that email verification is required when it is possible, and becomes a confusing variable name when applied outside of this context.

Instead of modelling this presumption, we should instead be representing the raw information in the database. To that end, I propose that we rename the boolean to email_verified, as that better represents the information that we need to store.

This will require a migration of the values, as when email_verified==True, email_verification_required==False and vice versa.

Ian Foote added 2 commits April 2, 2015 10:15
* Add `email_verified` boolean to track if the user's email address has
  been verified.
@LilyFirefly
Copy link

@adam-incuna @kevinetienne @nologo Review

@kevinetienne
Copy link
Contributor

Looks good to me, happy to merge if no other comment

kevinetienne pushed a commit that referenced this pull request Apr 2, 2015
Rename email_verification_required to email_verified
@kevinetienne kevinetienne merged commit 04bcf9b into master Apr 2, 2015
@kevinetienne kevinetienne deleted the email-verified branch April 2, 2015 10:03
@meshy
Copy link
Contributor Author

meshy commented Apr 7, 2015

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants