-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
fix(isEmail): fixed isFQDN
still checking email length when ignore_max_length
is true
#2128
Conversation
…_max_length` is `true`
isFQDN
still checking email length when ignore_max_length
is false
isFQDN
still checking email length when ignore_max_length
is true
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code changes look good, don't forget to document the new option for isFQDN
in the README
@WikiRik, thanks, documented |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks for the fix! 🎉
…_max_length` is `true` (#2170) profnandaa: clean-up #2128 --------- Co-authored-by: Said Akhmedbayev <[email protected]>
combined in #2170 |
fix(isEmail): fixed `isFQDN` still checking email length when `ignore_max_length` is `true` profnandaa: clean-up #2128 --------- Co-authored-by: Said Akhmedbayev <[email protected]> Co-authored-by: Said Akhmedbayev <[email protected]>
Fixed the issue when the
ignore_max_length
option was not honored (did not have any effect) since theisFQDN
function had its own check for the email parts length.Checklist