I believe you can validate nested fields with the array dot syntax: tags.new.0 would let you access the first element etc.

This PR allows for validating tags.new.%d, so for every element inside an array.

@franzliedke, i don't believe so since getValue() method retrieves associated element directly by attribute name (key in data/files array):

if (array_key_exists($attribute, $this->data))
{
    return $this->data[$attribute];
}
elseif (array_key_exists($attribute, $this->files))
{
    return $this->files[$attribute];
}

But even if that was a case, it's still only one element out of the array that might have an unknown size. Sure, you might generate rules based on the length of the input array, but that seems like an unnecessary hacking.

Ah, okay. Thanks for clarifying and sorry for not double-checking, guys.

+1 on this.

+1

@KaneCohen Using the above, how are custom error messages handled? The same way?

@scbenjamin, yes, the same way.

Taking example above:

$input = array('tags' => array(
    'new' => array('foo', 'bar1', 'baz'),
));
$val = Validator::make($input, array('tags.new' => 'required|alpha'));

Validation will fail because bar1 contains non alpha character.

validation.php file for language:

'custom' => array(
    'tags.new.alpha' => 'Tags may contain only alphabetical characters.'
),

👍

For the exists validation rule, wouldn't this run a lot of queries?

@taylorotwell, hmm, yeah. It seems like that thing (validate method to be exact) needs a rewrite so that when Validator hits DB-related rule it'll use "whereIn" to check for existence of the input and won't go through every item.