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

Introduce new field verified_at. #178

Closed
wants to merge 4 commits into from

Conversation

Konafets
Copy link
Contributor

@Konafets Konafets commented May 9, 2018

The new field will be added next to the current field verified, which stores the information if a user has been verified its email address. Internally the new field is used for verification by check the field against null.

The new field makes it possible to not only store if a user has been verified but also when.

Closes #177

The new field will be added next to the current field `verified`, which stores the information if a user has
been verified its email address. Internally the new field is used for verification by check the field against `null`.

The new field makes it possible to not only store _if_ a user has been verified but also _when_.

Closes jrean#177
@@ -303,7 +306,7 @@ protected function getUserByEmail($email, $table)
*/
protected function isVerified($user)
{
if ($user->verified == true) {
if ($user->verified == true && !is_null($user->verified_at)) {
Copy link
Contributor

@DariusIII DariusIII Sep 11, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe use $user->verified_at !== null?

@Konafets
Copy link
Contributor Author

Konafets commented Feb 1, 2019

@jrean What is the status here? Do you consider to merge this?

@jrean jrean closed this Mar 7, 2020
@Konafets
Copy link
Contributor Author

Konafets commented Mar 7, 2020

@jrean May I ask you why you are closing all these cool (mine and other) PRs without any explanation?

@jrean
Copy link
Owner

jrean commented Mar 9, 2020

Hi @Konafets
Because it is 2020 and this PR won't be merged as it it.
I wouldn't deal with this this way. I would rather change the code around the verified attribute to make it hold directly the timestamp or null.

If I update and implement it, I will not forget to credit your PR and your work.
Nothing wrong about closing a PR. It stays in the history of the project and I'm free to come back to it.

Thank you

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Switch from boolean to dateTime for verified field
3 participants