[5.2.29] Array validation : Required with

[azorgh]

Hello everybody.

I'm trying to use array validation introduced in Laravel 5.2.
But I think a bug is present. In fact, there is my array received by the request (debugged after my form submission) :

array:2 [▼
  "_token" => "oqsdgfxcGBSmxjaZO40wBmnYHfivaHv3"
  "fields" => array:2 [▼
    "fr" => array:3 [▼
      "name" => ""
      "slug" => ""
      "content" => "qdzd"
    ]
    "es" => array:3 [▼
      "name" => ""
      "slug" => ""
      "content" => ""
    ]
  ]
]

In my validation rules, I doing this :

return [
    'fields.*.content' => 'required_with:fields.*.name'
];

Normally in this case, the validation failed on the fields[fr][content], because the name was not set yet right ?

I'm so sorry if the bug is provided by between my chair and my desktop ...

[GrahamCampbell]

Are you using the very latest version?

[azorgh]

I'm using the 5.2.29.

[vlakoff]

ping @themsaid :)

[themsaid]

@pallmallshow

In your example fields[fr][content] is required only if fields[fr][name] has a value, I think you are trying to do that:

'fields.*.name' => 'required_with:fields.*.content'

[azorgh]

I've tried this rule but I had the same result.
I set content field but I keep the name field empty, and validation passed.
I set name field but I keep the content textarea empty, and validation passed.

[themsaid]

@pallmallshow you are right, bug catched and a fix was proposed in #13058

[themsaid]

@GrahamCampbell I think this one is resolved.

[azorgh]

Due to the PR merged yes, technically this one is resolved.
But when I run composer update, on a simply fresh install, I had the "old" code of Validation.php.
It's not so important for me for the moment ;)

[themsaid]

@pallmallshow it'll be available in the next patch release. 5.2.30

[azorgh]

Oh right no problem. Thanks ! Maybe I set issue closed when I can test on my case on the next release ?

[GrahamCampbell]

You can test the new code at any point. There doesn't have to be a tag.