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>
1 KiB
1 KiB
ArrayVal
ArrayVal()
Validates if the input is an array or if the input can be used as an array
(instance of ArrayAccess
or SimpleXMLElement
).
v::arrayVal()->validate([]); // true
v::arrayVal()->validate(new ArrayObject); // true
v::arrayVal()->validate(new SimpleXMLElement('<xml></xml>')); // true
Categorization
- Arrays
- Types
Changelog
Version | Description |
---|---|
2.0.0 | SimpleXMLElement is also considered as valid |
1.0.0 | Renamed from Arr to ArrayVal and validate only if the input can be used as an array (#1) |
0.3.9 | Created as Arr |
- Previously this rule considered
Traversable
andCountable
as valid inputs.
See also: