Custom Validation rules in Laravel 5.1

Question

I'm adding custom validation rules to my Laravel 5.1 application, and I currently have it set up like this in AppServiceProvider:

    Validator::extend('word_count', 'App\CustomValidators@wordCount');
    Validator::extend('required_if_not', 'App\CustomValidators@requiredIfNot');
    Validator::extend('date_in_year', 'App\CustomValidators@dateInYear');

This works, but I'm wondering if there is a better method I should be using with 5.1 rather than calling the Validator facade.

For example, calling to a view no longer requires me to call View::request('template', $viewData) or View::make('template', $viewData), but instead I can call view('template', $viewData), which cuts down on the number of namespaces I need to 'use' for my class. I can do something similar with redirects as well.

What is the best/cleanest method in Laravel 5.1 for adding custom validation rules?

Lisa, somethings the shortest way is not the best/cleanest. When the project is getting large is good to keep things in order instead putting extra effort-time just to save some characters. Take a look to this way: stackoverflow.com/questions/28417977/… — manix
– manix, Commented Oct 14, 2015 at 20:49
This question is part of a refactoring session that I'm doing on my project. It's less to minimize the number of characters that are used and more to learn best practices for Laravel 5.1. This application was upgraded from Laravel 4.1, so there's a lot in there that's still following those practices. — Lisa
– Lisa, Commented Oct 14, 2015 at 20:53

manix · Accepted Answer · 2015-10-14 21:15:23Z

1

Well, a probably solution here is to create a custom function (helper function as view()) to avoid the facade.

if (! function_exists('validator_ext')) {
    /**
     * Adding custom rules
     *
     * @param  string  $name
     * @param  array   $listener
     * @return \Illuminate\Validation\Factory
     */
    function validator_ext($name, $listener)
    {
        $validator = app('Illuminate\Validation\Factory');
        $validator->extend($name, $listener);
        return $validator;
    }
}

Now you are able to call it as:

validator_ext('word_count', 'App\CustomValidators@wordCount');

Another way without using a helper function is to instantiate the validator at boot method:

$validator = app('Illuminate\Validation\Factory');
$validator->extend('word_count', 'App\CustomValidators@wordCount');

edited Oct 14, 2015 at 21:15

answered Oct 14, 2015 at 21:06

manix

14.7k11 gold badges74 silver badges112 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Lisa Over a year ago

Thanks, both of those solutions look interesting. I'll play around with them and see how they go!

Collectives™ on Stack Overflow

Custom Validation rules in Laravel 5.1

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related