Email validation (RegEx)

[inlinecoder]

Hello guys 👋,

Not sure if that's the right spot to ask. By reading the source, I've noticed that email validation is very bare-bones, not sure if that's intentional or a small over-sight.

  if ((value && !/\S[^\s@]*@\S+\.\S+/.test(value)) || (!value && required)) {
    return t('validation:emailAddress')
  }

payload/packages/payload/src/fields/validations.ts

Line 193 in 3de1636

if ((value && !/\S[^\s@]*@\S+\.\S+/.test(value)) || (!value && required)) {

From my understanding, it's:

• It allows invalid emails
  --"[email protected]" (dot before @ is invalid)
  -- "[email protected]" (double dots are invalid)
• It rejects valid emails
  -- "[email protected]" (plus signs are valid)
  -- "üñîçødé@example.com" (Unicode is valid in local parts, per RFC 6531)
• It's too simple
  Email validation is tricky. Even RFC 5322-compliant regexes are long and ugly.

Please let me know what you think and whether it should be converted into an issue.

[kfiross]

@inlinecoder You can try my pacakge
https://www.npmjs.com/package/payload-field-validator

[kfiross]

@inlinecoder I used under the hood RFC 5322-compliant regexes in v0.2.3

[inlinecoder]

@kfiross, nice!
Can you show the file where you've incorporated those changes, please?

https://www.npmjs.com/package/payload-field-validator <- leads to 404.