Laravel: How to use the ignore rule in Form Request Validation

DatsunBing picture DatsunBing · Dec 5, 2017 · Viewed 16.3k times · Source

Laravel has a 'unique' rule with an 'except' clause. From the validation documentation, it takes this form:

unique:table,column,except,idColumn

My application has a 'shop' entity. When the user updates the shop's profile, I have a Form Request, with a validation rule configured as follows:

public function rules()
{
    return [
        'shop.name' => 'required|string|max:100|unique:shops,name,except,id',
    ];
}

(The primary key on my shops table is id).

The problem is that Laravel does not take any notice of the 'except' clause. This makes sense (sort of) since the shop ID is not being injected into the Form Request. I can inject id as just another form value, but that doesn't seem to work.

How can I get this rule working in a Form Request?

Answer

Cy Rossignol picture Cy Rossignol · Dec 5, 2017

To use the except clause to the unique rule, we need to provide the value of the field on the record that we want the rule to ignore directly in the rule itself.

So, if we want a unique name field for every record except for on the record that the request updates, we need to add the value of the ID field to ignore:

class UpdateShopRequest extends FormRequest
{
    ...
    public function rules() 
    {
        return [
            'shop.name' => 'unique:shops,name,' . $this->shop['id'],
        ];
    }
}

As shown, this rule will cause validation to fail if any row contains the same shop name unless the row's id matches $this->shop['id']. This example assumes that our form contains an array input field for the record's ID attribute because the question is performing validation on an array input:

<input type="hidden" name="shop[id]" value="{{ $shop->id }}">

...which lets us fetch the value within the request like we can with any other request. More typically, we pass the record ID as a route parameter, which we can retrieve using the request's route() method:

$shopId = $this->route('id');

...which works if we have a route defined similarly to:

Route::post('shops/{id}', ...);

The fourth parameter to the unique validation rule lets us specify which column the except clause applies to, and defaults to id, so we can leave it off if we're just comparing the record's ID.

The rule looks a bit clumsy when we just concatenate the column value, especially for a field with a lot of other rules. Since version 5.3, Laravel provides a more elegant syntax to create a unique rule with an except clause:

use Illuminate\Validation\Rule;
...
return [
    'shop.name' => [ 
        'required', 
        'string', 
        'max:100', 
        Rule::unique('shops', 'name')->ignore($shopId, 'optional_column'), 
    ],
];