From fc017846c4b5ecf1faf728b1f709fa7fef7ff901 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Santiago=20San=20Mart=C3=ADn?= Date: Wed, 14 May 2025 22:35:37 -0300 Subject: [PATCH] [Validator] avoid broken rendering of inline types in UniqueEntity This PR fixes an issue in the documentation where inline type annotations like | ``string`` | were not rendering correctly due to reStructuredText interpreting the | characters as substitution references. Changes: Replaced | ``string`` | with a more reliable format: boolean, string or array Ensures consistent rendering across Sphinx and other reST parsers This improves readability and avoids confusion when displaying valid type options in inline documentation. --- reference/constraints/UniqueEntity.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/reference/constraints/UniqueEntity.rst b/reference/constraints/UniqueEntity.rst index 2c9aeccd755..0e1731371a5 100644 --- a/reference/constraints/UniqueEntity.rst +++ b/reference/constraints/UniqueEntity.rst @@ -277,7 +277,7 @@ each with a single field. ``ignoreNull`` ~~~~~~~~~~~~~~ -**type**: ``boolean`` | ``string`` | ``array`` **default**: ``true`` +**type**: ``boolean``, ``string`` or ``array`` **default**: ``true`` If this option is set to ``true``, then the constraint will allow multiple entities to have a ``null`` value for a field without failing validation.