Skip to content
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

Update regex e-mail #331

Merged
merged 1 commit into from
May 19, 2024
Merged

Update regex e-mail #331

merged 1 commit into from
May 19, 2024

Conversation

PGijsbers
Copy link
Contributor

Allow a dash in the domain name, e.g., [email protected]. Might want to use some e-mail parsing library for this instead, but this at least fixes this oversight.

Allow a dash in the domain name, e.g., `[email protected]`.
Might want to use some e-mail parsing library for this instead, but this at least fixes this oversight.
Copy link
Collaborator

@josvandervelde josvandervelde left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This does allow some invalid email addresses, such as [email protected].

It is probably better to allow invalid addresses rather than disallowing valid addresses. So I'd approve it - hopefully we'll use an email-parsing lib indeed in the new code.

@PGijsbers PGijsbers merged commit d4991c3 into master May 19, 2024
3 checks passed
@PGijsbers PGijsbers deleted the PGijsbers-patch-2 branch May 19, 2024 19:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants