ULID
Validates that a value is a valid Universally Unique Lexicographically Sortable Identifier (ULID).
Applies to | property or method |
Class | Ulid |
Validator | UlidValidator |
Basic Usage
1 2 3 4 5 6 7 8 9 10
// src/Entity/File.php
namespace App\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class File
{
#[Assert\Ulid]
protected string $identifier;
}
Note
As with most of the other constraints, null
and empty strings are
considered valid values. This is to allow them to be optional values.
If the value is mandatory, a common solution is to combine this constraint
with NotBlank.
Options
format
type: string
default: Ulid::FORMAT_BASE_32
The format of the ULID to validate. The following formats are available:
Ulid::FORMAT_BASE_32
: The ULID is encoded in base32 (default)Ulid::FORMAT_BASE_58
: The ULID is encoded in base58Ulid::FORMAT_RFC4122
: The ULID is encoded in the RFC 4122 format
7.2
The format
option was introduced in Symfony 7.2.
groups
type: array
| string
default: null
It defines the validation group or groups of this constraint. Read more about validation groups.
message
type: string
default: This is not a valid ULID.
This message is shown if the string is not a valid ULID.
You can use the following parameters in this message:
Parameter | Description |
---|---|
{{ value }} |
The current (invalid) value |
{{ label }} |
Corresponding form field label |
normalizer
type: a PHP callable default: null
This option allows to define the PHP callable applied to the given value before checking if it is valid.
For example, you may want to pass the 'trim'
string to apply the
trim PHP function in order to ignore leading and trailing
whitespace during validation.
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.