Skip to content

Commit

Permalink
Explain the limitations of the custom messages in UniqueEntity
Browse files Browse the repository at this point in the history
  • Loading branch information
javiereguiluz authored and wouterj committed Oct 6, 2016
1 parent 36a460d commit 4c10ea8
Showing 1 changed file with 12 additions and 1 deletion.
13 changes: 12 additions & 1 deletion reference/constraints/UniqueEntity.rst
Original file line number Diff line number Diff line change
Expand Up @@ -132,7 +132,18 @@ message

**type**: ``string`` **default**: ``This value is already used.``

The message that's displayed when this constraint fails.
The message that's displayed when this constraint fails. This message is always
mapped to the first field causing the violation, even when using multiple fields
in the constraint.

.. versionadded:: 3.1
The ability to include the invalid value into the message was introduced
in Symfony 3.1.

Messages can include the ``{{ value }}`` placeholder to display a string
representation of the invalid entity. If the entity doesn't define the
``__toString()`` method, the following generic value will be used: *"Object of
class __CLASS__ identified by <comma separated IDs>"*

em
~~
Expand Down

0 comments on commit 4c10ea8

Please sign in to comment.