Part #2: How to use Laravel's Validator::extend method for custom validation

Harish Kumar · · 5930 Views

Validation is important in any application as it validates a form before performing actions on it. It allows the user to know their input is accurate and confident about the operation they are about to do.

There are many ways to validate form requests in Laravel. One of them is closure-based validation which I have already explained it. You can read about it from the below article link:

  1. Part #1: Closure-based Laravel Validation

In this article, I will show how easily Laravel handles custom validation using the Validator::extend method. It allows us to register custom validation rules globally. It allows two different ways to extend custom validation using a validator.

The first is passing a closure to the extend method on the class. It is a good option when your project is small and you want to keep the logic together.

The second most preferred way is to pass in the name of the class instead of the closure function. It means you have to extend the validator in one place and keep the logic for validation in a separate class.

Let’s look at setting up both of these methods!

Extending the Validator using closure

As I mentioned above, here we pass a closure to the extend method on the validator class:

Validator::extend('match_current_password', function($attribute, $value, $parameters, $validator) {
    if (!auth()->check()) {
        return false;

    return Hash::check($value, auth()->user()->password);

The first argument of the extend method is the name of the validation rule and the second is the closure.

The closure accepts three arguments:

$attribute: The name of the attribute that you are validating.

$value: The value of the attribute

$parameters: An array of parameters that can be passed to the rule.

Extending the Validator using class

Extending the validator using closure is nice and easy, but resolving from a class is much prefered. What are the benefits of resolving from a class? Well, I think there are two reasons for this:

  1. Easier to manage multiple extensions

  2. Always extend in a consistent way

So the first thing to do is to create your class for validation logic:


namespace App\Validator;

use Illuminate\Support\Facades\Hash;

class MatchCurrentPassword
    public function validate($attribute, $value, $parameters, $validator)
        if (! auth()->check()) {
            return false;

        return Hash::check($value, auth()->user()->password);

Now pass, this class in the validator extend method:

Validator::extend('match_current_password', MatchCurrentPassword::class);

Please login or create new account to add your comment.

You may also like:

Laravel Pint & VS Code: Automate Your Code Formatting

Laravel Pint is an opinionated PHP code style fixer built on top of PHP-CS-Fixer, designed to simplify the process of ensuring clean and consistent code style in Laravel projects. (...)
Harish Kumar

Laravel Clockwork: A Deep Dive into Debugging, Profiling Skills and Best Practices

In the world of web development, building complex applications often comes with the challenge of identifying and resolving performance bottlenecks. This is where a reliable debugging (...)
Harish Kumar

Effortless PDF Generation in Laravel: A Guide to Using Spatie/Browsershot Package

Looking to generate or export PDF files using Laravel? Look no further! In this article, we'll guide you through using the Laravel spatie/browsershot package to seamlessly convert (...)
Harish Kumar

Part #3: Rule objects based custom validation in Laravel

Laravel comes with multiple ways to add custom validation rules to validate form request inputs. I have already explained some of the ways in the following article links:
Harish Kumar

Part #1: Closure-based Custom Laravel Validation

While I was working with Laravel, validation using closure came to my mind, and I know it will be helpful to you. This tutorial assists you with all what is the difference between (...)
Harish Kumar

How to use the enumerations(Enums) of PHP 8.1 in Laravel?

The release of PHP 8.1 brings native enumerations to PHP. There is no more requirement for custom solutions in your Laravel projects since the Laravel v8.69 release has you back. (...)
Harish Kumar