fix: use *bool for EmailVerified in CreateUserRequestDto#270
Merged
Conversation
…uired validator rejecting false go-playground/validator's required tag rejects the zero value of bool (false), causing user creation to always fail with a validation error when emailVerified is set to false. Switching to *bool with ZeroIfNil makes the field optional and defaults to false when omitted. Signed-off-by: karo <karolin.kostial@gmail.com>
The127
force-pushed
the
fix/create-user-email-verified-validation
branch
from
9b71190 to
f591e58
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
EmailVerified boolwithvalidate:"required"caused user creation to always fail whenemailVerified: falsewas sent, because go-playground/validator rejects the zero value of a bool*boolwith no required tag; handler usesutils.ZeroIfNilto default tofalsewhen omittedTest plan
emailVerified: true— should still workemailVerifiedat all — should default tofalse