Negative
Warning: You are browsing the documentation for Symfony 4.x, which is no longer maintained.
Read the updated version of this page for Symfony 7.2 (the current stable version).
4.3
The Negative
constraint was introduced in Symfony 4.3.
Validates that a value is a negative number. Zero is neither positive nor negative, so you must use NegativeOrZero if you want to allow zero as value.
Applies to | property or method |
Class | Negative |
Validator | LesserThanValidator |
Basic Usage
The following constraint ensures that the withdraw
of a bank account
TransferItem
is a negative number (lesser than zero):
1 2 3 4 5 6 7 8 9 10 11 12
// src/Entity/TransferItem.php
namespace App\Entity;
use Symfony\Component\Validator\Constraints as Assert;
class TransferItem
{
/**
* @Assert\Negative
*/
protected $withdraw;
}
Available Options
groups
type: array
| string
It defines the validation group or groups of this constraint. Read more about validation groups.
message
type: string
default: This value should be negative.
The default message supplied when the value is not less than zero.
You can use the following parameters in this message:
Parameter | Description |
---|---|
{{ compared_value }} |
Always zero |
{{ compared_value_type }} |
The expected value type |
{{ value }} |
The current (invalid) value |
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.