feature #7057 [DoctrineBridge] Document the new entityClass option (ogizanagi)

wouterj · wouterj · commit 13acf3ee451c · 2016-11-10T20:59:54.000+01:00
This PR was merged into the master branch. Discussion ---------- [DoctrineBridge] Document the new `entityClass` option Waiting for symfony/symfony#15002 to be merged. Commits ------- a9c2fc2 [DoctrineBridge] Document the new `entityClass` option
diff --git a/reference/constraints/UniqueEntity.rst b/reference/constraints/UniqueEntity.rst
@@ -12,6 +12,7 @@ using an email address that already exists in the system.
 |                | - `message`_                                                                        |
 |                | - `em`_                                                                             |
 |                | - `repositoryMethod`_                                                               |
+|                | - `entityClass`_                                                                    |
 |                | - `errorPath`_                                                                      |
 |                | - `ignoreNull`_                                                                     |
 |                | - `payload`_                                                                        |
@@ -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
 ~~~~~~~~~
 
