Skip to content

[DoctrineBridge] Document the new entityClass option #7057

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

Merged
merged 1 commit into from
Nov 10, 2016
Merged

[DoctrineBridge] Document the new entityClass option #7057

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 15 additions & 0 deletions reference/constraints/UniqueEntity.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@ using an email address that already exists in the system.
| | - `message`_ |
| | - `em`_ |
| | - `repositoryMethod`_ |
| | - `entityClass`_ |
| | - `errorPath`_ |
| | - `ignoreNull`_ |
| | - `payload`_ |
Expand Down Expand Up @@ -164,6 +165,20 @@ The name of the repository method to use for making the query to determine
the uniqueness. If it's left blank, the ``findBy`` method will be used.
This method should return a countable result.

entityClass
~~~~~~~~~~~

**type**: ``string`` **default**: ``null``

.. versionadded:: 3.2
The ``entityClass`` option was introduced in Symfony 3.2.

By default, the query performed to ensure the uniqueness uses the repository of
the current class instance. However, in some cases, such as when using Doctrine
inheritance mapping, you need to execute the query in a different repository.
Use this option to define the fully-qualified class name (FQCN) of the Doctrine
entity associated with the repository you want to use.

errorPath
~~~~~~~~~

Expand Down