You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changing any property on User extended model changes the emailVerified property to false #3063
I've I've recently migrated to Loopback 3. I'm Postgresql database. One of my tests is failing with a strange behaviour. I've raised this issue on Stackoverflow as well.
I have a Member model that extends the User model. Whenever I change any property on my Member model, the emailVerified changes from true to false
I've also tried with updateAttributes but the results are the same.
I found that in user model code, emailChanged is returning true because ctx.data.email is undefined. Changing it to first check if it exists does solve my problem.
Our password reset is now broken because of this too. emailVerified set to 0.
Just tried to upgrade from our pinned 2.29.1 version of loopback to the latest 2.x version. Was pinned because of a previous regression wrt PUT/PATCH endpoint verbs. Trying to get back up to latest.
Tried to explicitly set emailVerified = 1 in our custom reset function we created, but no dice (must be being reset in some "after" middleware in User? We extend with Person).
Loopback 2.36.2 is not backwards compatible with 2.29.1. Sigh.
Activity
mackwan84 commentedon Jan 3, 2017
+1 I am facing the same problem after update to 3.0.
hussainak commentedon Jan 3, 2017
+1
notbrain commentedon Jan 3, 2017
+1 in 2.36.2
Our password reset is now broken because of this too.
emailVerifiedset to 0.Just tried to upgrade from our pinned 2.29.1 version of loopback to the latest 2.x version. Was pinned because of a previous regression wrt PUT/PATCH endpoint verbs. Trying to get back up to latest.
Tried to explicitly set
emailVerified = 1in our custom reset function we created, but no dice (must be being reset in some "after" middleware in User? We extend with Person).Loopback 2.36.2 is not backwards compatible with 2.29.1. Sigh.
lleopardi commentedon Jan 4, 2017
+1
lschricke commentedon Jan 4, 2017
Same issue here.
davidcheung commentedon Jan 4, 2017
once this lands it should fix
#3053
davidcheung commentedon Jan 10, 2017
this bug should be fixed in #3053 or in (2.x) #3072, please ping me in this thread if issue persists to reopen. Closing now.