fix: update email regex to support special characters #12181
Merged
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.
What?
It's impossible to create a user with special characters in their email in Payload CMS 3.35.0.
The issue is that currently the regex looks like this:
...payload/packages/payload/src/fields/validations.ts (line 202-203):
const emailRegex = /^(?!...)[\w.%+-]+@a-z0-9?(?:.a-z0-9?).[a-z]{2,}$/i
This allows users that have the following characters in their email to be created:
%, ., +, -
The regex needs to get updated to the following:
const emailRegex = /^(?!...)[\w!#$%&'+/=?^{|}~.-]+@a-z0-9?(?:.a-z0-9?)*.[a-z]{2,}$/i`
This way all special characters `!#$%&'*+/=?^_{|}~.-`` are hereby OK to have in the email.
I've added more test-cases to cover a couple of more scenarios in the forked repo.
Why?
The regex is missing some special characters that are allowed according to standards.
How?
Fixes #
#12180