Traverse
Object properties are only validated if they are accessible, either by being public or having public accessor methods (e.g. a public getter). If your object needs to be traversed to validate its data, you can use this constraint.
Applies to |
|
Class |
|
Basic Usage
In the following example, create two classes BookCollection and Book
that all have constraints on their properties.
When the object implements \Traversable (like here with its child
\IteratorAggregate), its traversal strategy will implicitly be set and the
object will be iterated over without defining the constraint.
It’s mostly useful to add it to be explicit or to disable the traversal using
the traverse option.
If a public getter exists to return the inner books collection like
getBooks(): Collection, the Valid constraint
can be used on the $books property instead.
Options
The groups option is not available for this constraint.
traverse
type: boolean default: true
Instances of \Traversable are traversed by default, use this option to
disable validating:
payload
type: mixed default: null
This option can be used to attach arbitrary domain-specific data to a constraint. The configured payload is not used by the Validator component, but its processing is completely up to you.
For example, you may want to use several error levels to present failed constraints differently in the front-end depending on the severity of the error.