Originally released in Laravel 5.5, custom validation rule objects offer a fluent alternative to string-based rules. In its simplest form, the Password rule object replaces string-based validation rules:
<?php
// String-based
$request->validate([
'password' => 'required|string|confirmed|min:8',
]);
// Using the Password rule object
$request->validate([
'password' => ['required', 'confirmed', Password::min(8)],
]);
In addition to replacing string rules with a fluent password rule object, the custom password rule object includes built-in methods for ensuring strong passwords:
<?php
$request->validate([
'password' => [
'required',
'confirmed',
Password::min(8)
->mixedCase()
->letters()
->numbers()
->symbols()
->uncompromised(),
],
]);
Never write custom regex logic for typical scenarios such as requiring mixed-case, letters, symbols, etc. The cherry on the top is the uncompromised() method which checks the password against a verification API to see if the password appears in data leaks. The release will ship with a NotPwnedVerifier implementation which uses the Have I Been Pwned API.
In addition to this excellent new custom validation object, Pull Request #36960 contains some good examples of using Laravel to test API calls and validation.
Depending on when Laravel 8.39 gets tagged, this feature might be available at the time of publication Tuesday, April 27th. Keep your eyes peeled for the release of this awesome feature!
Laravel laravel8 by laravelnote.