Nov 10, 2016 · Oct 13, 2016
diff --git a/reference/constraints/UniqueEntity.rst b/reference/constraints/UniqueEntity.rst
 |                | - `message`_                                                                        |
 |                | - `em`_                                                                             |
 |                | - `repositoryMethod`_                                                               |
 |                | - `entityClass`_                                                                    |
 |                | - `errorPath`_                                                                      |
 |                | - `ignoreNull`_                                                                     |
 |                | - `payload`_                                                                        |
 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
 ~~~~~~~~~
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 DownExpand 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