Corey Shuman

This is a promising solution if we could figure out a way to standardize it for our projects. https://github.com/django/django/blob/master/django/core/validators.py#L164 Plus lots of examples and resources here: http://emailregex.com/

I would like to humbly propose a solution which performs as well as the RFC5322 Official Standard (in my particular test set) but is much easier to understand and verify....

Hyphen support I'm not as concerned with, in terms of hitting that balance of simplicity vs. complete accuracy to RFC 5322. A false positive is not a big deal, vs...

I don't disagree. My goal in this particular task was to discover a good front-end validation for email which gives a user immediate feedback to avoid typos, not necessarily to...

@michaelachrisco 3 years later and this is still a recurring issue in projects. Now that we have boilerplates to implement a standard, I think this is a good time to...

Adding that I agree with Justin Schiff's assessment here: > @coreyshuman I would normally agree, but what i'm trying to make clear here is that complicated email regex is not...

I noticed we do have an example documented in best practices here: https://github.com/Shift3/standards-and-practices/tree/main/best-practices/development-tools/validation#code-example For this to be a completed standard, we should include a definition for our goal on what...

Oh yeah I like extending this rule to cover magic functions we find online.

@mwallert @ryekerjh I think that's a great idea. We should make sure the new employee on-boarding / `getting started` hits that `Rules to Code By` folder.

@mwallert @ryekerjh I'm continuing to find things that don't quite need a full dedicated file, but would be considered standards. Instead of a `Rules to Code By` folder, I think...