Rename email_verification_required to email_verified #118
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 variable
User.email_verification_requiredis 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==Falseand vice versa.