IsFalse

IsFalse

Validates that a value is false. Specifically, this checks to see if the value is exactly false, exactly the integer 0, or exactly the string '0'.

Also see IsTrue.

Applies toproperty or method
Options
ClassSymfony\Component\Validator\Constraints\IsFalse
ValidatorSymfony\Component\Validator\Constraints\IsFalseValidator

Basic Usage

The IsFalse constraint can be applied to a property or a “getter” method, but is most commonly useful in the latter case. For example, suppose that you want to guarantee that some state property is not in a dynamic invalidStates array. First, you’d create a “getter” method:

  1. protected $state;
  2. protected $invalidStates = [];
  3. public function isStateInvalid()
  4. {
  5. return in_array($this->state, $this->invalidStates);
  6. }

In this case, the underlying object is only valid if the isStateInvalid() method returns false:

  • Annotations

    1. // src/Entity/Author.php
    2. namespace App\Entity;
    3. use Symfony\Component\Validator\Constraints as Assert;
    4. class Author
    5. {
    6. /**
    7. * @Assert\IsFalse(
    8. * message = "You've entered an invalid state."
    9. * )
    10. */
    11. public function isStateInvalid()
    12. {
    13. // ...
    14. }
    15. }
  • YAML

    1. # config/validator/validation.yaml
    2. App\Entity\Author:
    3. getters:
    4. stateInvalid:
    5. - 'IsFalse':
    6. message: You've entered an invalid state.
  • XML

    1. <!-- config/validator/validation.xml -->
    2. <?xml version="1.0" encoding="UTF-8" ?>
    3. <constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping"
    4. xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    5. xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping https://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd">
    6. <class name="App\Entity\Author">
    7. <getter property="stateInvalid">
    8. <constraint name="IsFalse">
    9. <option name="message">You've entered an invalid state.</option>
    10. </constraint>
    11. </getter>
    12. </class>
    13. </constraint-mapping>
  • PHP

    1. // src/Entity/Author.php
    2. namespace App\Entity;
    3. use Symfony\Component\Validator\Constraints as Assert;
    4. use Symfony\Component\Validator\Mapping\ClassMetadata;
    5. class Author
    6. {
    7. public static function loadValidatorMetadata(ClassMetadata $metadata)
    8. {
    9. $metadata->addGetterConstraint('stateInvalid', new Assert\IsFalse([
    10. 'message' => "You've entered an invalid state.",
    11. ]));
    12. }
    13. public function isStateInvalid()
    14. {
    15. // ...
    16. }
    17. }

Note

As with most of the other constraints, null is considered a valid value. This is to allow the use of optional values. If the value is mandatory, a common solution is to combine this constraint with NotNull.

Options

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 false.

This message is shown if the underlying data is not false.

You can use the following parameters in this message:

ParameterDescription
{{ 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.

This work, including the code samples, is licensed under a Creative Commons BY-SA 3.0 license.