mirror of https://github.com/Respect/Validation.git synced 2024-06-13 11:12:18 +02:00

Currently, the Key rule has a third parameter that allows the validation
of the wrapped rule to be optional, meaning that the validation will
only happen if the key exists. That parameter makes the rule harder to
understand at times.

I'm splitting the Key rule into Key, KeyExists, and KeyOptional. That
way, it becomes apparent when someone wants only to validate whether a
key exists or if they're going to validate the value of the key only
when it exists.

I deliberately didn't create an abstract class because those rules are
different enough not to have an abstraction. In fact, I can see myself
deleting the  "AbstractRelated" in the upcoming changes.

With these changes, the KeySet rule will not accept validating if the
key exists or validating the value only if the key exists. I should
refactor that soon, and I will likely need to create a common interface
for Key, KeyExists, and KeyOptional.

Signed-off-by: Henrique Moody <henriquemoody@gmail.com>

2024-03-04 00:06:18 +01:00

1.3 KiB

Raw Permalink Blame History

Each

Each(Validatable $rule)

Validates whether each value in the input is valid according to another rule.

$releaseDates = [
    'validation' => '2010-01-01',
    'template'   => '2011-01-01',
    'relational' => '2011-02-05',
];

v::each(v::dateTime())->validate($releaseDates); // true

You can also validate array keys combining this rule with Call:

v::call('array_keys', v::each(v::stringType()))->validate($releaseDates); // true

Note

This rule uses IterableType and NotEmpty internally. If an input is non-iterable or empty, the validation will fail.

Categorization

Arrays
Nesting
Transformations

Changelog

Version	Description
3.0.0	Rejected `stdClass`, non-iterable. or empty iterable values
2.0.0	Remove support for key validation
0.3.9	Created

1.3 KiB Raw Permalink Blame History

Each

Note

Categorization

Changelog

1.3 KiB

Raw Permalink Blame History