Array element validation doesn't pass even when it should

Question

I have a trouble validating an array members in validation for Laravel. For array itself it passes, but for elements themselves, it fails.

Open json in console, shows structure of data being sent. It's clearly a integer. Since it's associative array, not sure how it even finds it's value as show in error handling red rectangle on the bottom of the page.

Here is my validation logic:

$validation = Validator::make(
            $request->all(),
            [
                'load_place' => 'required|max:255',
                "unload_place" => 'required|max:255',
                "comment" => 'required|max:255',
                'time_in' => 'required',
                'time_out' => 'required',
                "vehicles" => 'required|array',
                "vehicles.*" => "required|integer",
                'operator_id' => 'required|integer',
                'sec_id' => 'required|integer'
            ]
        );

And here is how it's returned:

    if($validation->fails()){
    
                    $response = array(
                        "message" => "Failed",
                        "errors" => $errors,
                        "test" => $request->vehicles[0]
                    );
                    return response()->json($response);
    
                }

That request[0], is that number at the bottom.

Edit1:

Keys in that marked array, are set on frontend, they are not not predefined. They can be whatever.

Donkarnash · Accepted Answer · 2022-05-30 12:37:44Z

1

Change "vehicles.*" => "required|integer", to "vehicles.*.vehicle_id" => "required|integer", and it should work.

Keys is set on frontend, they are not not predefined. That what i am trying to say.

Try to replace "vehicles.*" => "required|integer", with new Rule::forEach rule for nested array data - guess it should work.

"vehicles.*" => Rule::forEach(function($value, $attribute) {
    return [
        Rule::integer()->min(1)   //min(1) as eg if it's for an id field which cannot be 0
    ];
}),

edited May 30, 2022 at 12:37

answered May 30, 2022 at 11:39

Donkarnash

12.9k5 gold badges30 silver badges43 bronze badges

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

6 Comments

Veljko Stefanovic Over a year ago

I know that. What if placeholder name for a value, in this case "vehicle_id" is different? e.g. something else as placeholder name?

Donkarnash Over a year ago

Whatever key you are using inside individual objects of vehicles array you need to use that in the validation rules. If you are using foo as the key like [{foo:1},{foo:5}] then the validation rule should be "vehicles.*.foo" => "required|integer"

Veljko Stefanovic Over a year ago

Keys is set on frontend, they are not not predefined. That what i am trying to say.

Donkarnash Over a year ago

You can try "vehicles.*.*" => "required|integer" if it works. Otherwise you may have to write your own custom validation rule.

Donkarnash Over a year ago

@VeljkoStefanovic Have updated the answer to make use of new Rule::forEach() for validating arrays with nested data. Check if that works

|

Collectives™ on Stack Overflow

Array element validation doesn't pass even when it should

1 Answer 1

6 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

6 Comments

Your Answer

Sign up or log in

Post as a guest

Related