Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explain the limitations of the custom messages in UniqueEntity #6932

Closed
wants to merge 4 commits into from
Closed

Explain the limitations of the custom messages in UniqueEntity #6932

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ef0ea78
Explain the limitations of the custom messages in UniqueEntity
javiereguiluz Aug 30, 2016
4bd081e
Reworded everything
javiereguiluz Aug 30, 2016
1f91326
Minor reword to be more concise
javiereguiluz Aug 31, 2016
a903b01
Added the versionadded directive
javiereguiluz Oct 4, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion reference/constraints/UniqueEntity.rst
View file
Open in desktop
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