Can we have a containsEmail() and containsURL()?

[U-4-E-A]

Use case - you don't want passwords to contain emails or websites (too guessable). Would like to interrogate the string to see if it contains than that just is. Thanks.

[heanzyzabala]

You can easily use:

validator.isEmail('[email protected]') || validator.isUrl('https://google.com')

before doing anything with the password.

[U-4-E-A]

You can easily use:

validator.isEmail('[email protected]') || validator.isUrl('https://google.com')

before doing anything with the password.

This checks if the string is an email or url, rather than checking to see if the string contains an email or url.

import isEmail from 'validator/lib/isEmail'

isEmail('[email protected]') // true
isEmail(':::[email protected]:::') // false

[Chetan-B-B]

@U-4-E-A I got an idea can u assign me to this issue?

[WikiRik]

@Chetan-B-B there are already two PRs for this, maybe you could review those and see if your idea aligns?

[U-4-E-A]

For those it may help, I was planning on using this for testing for emails/urls in passwords. This can be done using user input with zxcvbn-ts, which also provides l33t matching functionality.

[rubiin]

I'm not sure how I feel about this . AFAIR this kind of stuff has been discussed in the past and we decided not to add more functionalities to the package, especially such features that can be implemented by the end-user (customized through the existing validator method). To me, this doesn't sound like a necessary addition, given that it's non-blocking & not very complex to implement on your own :) You can see the input from @profnandaa here https://github.com/validatorjs/validator.js/pull/1886#issuecomment-1105951094

[pano9000]

ok, seeing as those PRs have been shut down, I don't think there is any sense in having the issue still open. thanks for your report, but closing it as "WONTDO", as outlined here https://github.com/validatorjs/validator.js/pull/1886#issuecomment-1105951094