Type
Warning: You are browsing the documentation for Symfony 3.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.2 (the current stable version).
Validates that a value is of a specific data type. For example, if a variable
should be an array, you can use this constraint with the array
type
option to validate this.
Applies to | property or method |
Options | |
Class | Type |
Validator | TypeValidator |
Basic Usage
This will check that id
is an instance of Ramsey\Uuid\UuidInterface
,
firstName
is of type string
and age
is an integer
.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
// src/AppBundle/Entity/Author.php
namespace AppBundle\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class Author
{
/**
* @Assert\Type("Ramsey\Uuid\UuidInterface")
*/
protected $id;
/**
* @Assert\Type("string")
*/
protected $firstName;
/**
* @Assert\Type(
* type="integer",
* message="The value {{ value }} is not a valid {{ type }}."
* )
*/
protected $age;
}
Options
type
type: string
[default option]
This required option is either the FQCN (fully qualified class name) of some PHP
class/interface or a valid PHP datatype (checked by PHP's is_()
functions):
- array
- bool
- callable
- float
- double
- int
- integer
- iterable
- long
- null
- numeric
- object
- real
- resource
- scalar
- string
Also, you can use ctype_()
functions from corresponding
built-in PHP extension. Consider a list of ctype functions:
Make sure that the proper locale is set before using one of these.
groups
type: array
| string
It defines the validation group or groups this constraint belongs to. Read more about validation groups.
message
type: string
default: This value should be of type {{ type }}.
The message if the underlying data is not of the given type.
You can use the following parameters in this message:
Parameter | Description |
---|---|
{{ value }} |
The current (invalid) value |
{{ type }} |
The expected type |
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.