WARNING: You are browsing the documentation for Symfony 2.7 which is not maintained anymore. Consider upgrading your projects to Symfony 5.2.

IsFalse

2.7 version

Maintained

4.4 5.1 5.2 current 5.3 dev

Unmaintained

2.3 2.7 2.8 3.0 3.1 3.2 3.3 3.4 4.0 4.1 4.2 4.3 5.0

IsFalse
- Basic Usage
- Options
  - message
  - payload

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 to	property or method
Options	message payload
Class	`Symfony\Component\Validator\Constraints\IsFalse`
Validator	`Symfony\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:

protected $state;

protected $invalidStates = array();

public function isStateInvalid()
{
    return in_array($this->state, $this->invalidStates);
}

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

Annotations

// src/AppBundle/Entity/Author.php
namespace AppBundle\Entity;

use Symfony\Component\Validator\Constraints as Assert;

class Author
{
    /**
     * @Assert\IsFalse(
     *     message = "You've entered an invalid state."
     * )
     */
     public function isStateInvalid()
     {
        // ...
     }
}

YAML

# src/AppBundle/Resources/config/validation.yml
AppBundle\Entity\Author:
    getters:
        stateInvalid:
            - 'IsFalse':
                message: You've entered an invalid state.

XML

<!-- src/AppBundle/Resources/config/validation.xml -->
<?xml version="1.0" encoding="UTF-8" ?>
<constraint-mapping xmlns="http://symfony.com/schema/dic/constraint-mapping"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://symfony.com/schema/dic/constraint-mapping http://symfony.com/schema/dic/constraint-mapping/constraint-mapping-1.0.xsd">

    <class name="AppBundle\Entity\Author">
        <getter property="stateInvalid">
            <constraint name="IsFalse">
                <option name="message">You've entered an invalid state.</option>
            </constraint>
        </getter>
    </class>
</constraint-mapping>

PHP

// src/AppBundle/Entity/Author.php
namespace AppBundle\Entity;

use Symfony\Component\Validator\Mapping\ClassMetadata;
use Symfony\Component\Validator\Constraints as Assert;

class Author
{
    public static function loadValidatorMetadata(ClassMetadata $metadata)
    {
        $metadata->addGetterConstraint('stateInvalid', new Assert\IsFalse());
    }
}

Options¶

message¶

type: string default: This value should be false.

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

payload¶

type: mixed default: null

New in version 2.6: The payload option was introduced in Symfony 2.6.

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.