Laravel 5.8 override email validation / use 5.7 rules

I'd look at binding a new class into the container. You can basically tell laravel "when this class is requested, give it this other class instead." So you can make a new "email" validation rule, and whenever laravel tries to load it it will load your custom class instead of the original. So one alteration and everybody can keep using the same terminology they have been.

$this->app->singleton(
    'Laravel\Spark\Contracts\Interactions\Settings\Profile\UpdateContactInformation',
    'App\Http\SparkExtensions\UpdateContactInformation'
);

Here's one where I'm substituting one of Laravel Sparks classes (the first one) with my own (2nd one) in the app service provider's register() method. So the first class would be the original laravel validation email rule and the 2nd one would be your custom rule class. You can just copy the old email rule if you want.

https://laravel.com/docs/5.8/container#binding

Email validation is about the easiest there is and built into PHP. If 5.8 doesn't fit you need, create a custom rule and add the code.

filter_var($email, FILTER_VALIDATE_EMAIL)

https://www.php.net/manual/en/function.filter-var.php

@CRONIX - Great, that looks like a solid solution, thanks

@JEKINNEY - thanks for your reply. My issue is with how to overwrite the built in email validation filter, to avoid having to document (and enforce) our own custom rule.

As a side note, this really should have come with a warning in the release notes for 5.8. Yes its technically valid, but i image the vast majority of users will not want this behavior.

You can actually use the email:filter validation rule and it will then validate emails without TLD as "false" / invalid emails.