2 ms·
But you don't want "implicitly verified", when there exist any code to which the difference between "verified" and "not verified" matters in some way. In your
by TeMPOraL 2y ago
But you don't want "implicitly verified", when there exist any code to which the difference between "verified" and "not verified" matters in some way.
In your own example, if you happen to use e-mail verification as proxy for user verification, then the very code that creates VerifiedUser instances would want to have VerifiedEmail as input!
- bvrmn 2y agoYou don't need VerifiedUser in the moment user click verification link. It's a state changing action. You get verified user from db and work with it later.
- TeMPOraL 2y agoFine. It still has merit that the code pulling verified user data from verified users table returns VerifiedUser objects, so the code processing them is clear about its assumptions, and won't accidentally get reused or refactored in UnverifiedUser flows.