[Validator] Add docs for bridge twig validator #20836

[sfmok]

This pull request adds documentation for the new Twig Validator constraint introduced in the Twig Bridge.

Changes:

• Added a page to document the Twig validator constraint, including:
• Installation instructions for the symfony/twig-bridge package.
• Usage of the constraint in Symfony applications.
• Detailed options available, including message and skipDeprecations.
• Updated index.rst to include the new page under the "Topics" section for the Twig Bridge.

Related Issue:
Issue #20836 - Add docs for Twig validator

Related PR:
Symfony PR #58805 – Introduced the Twig validator constraint in the Twig Bridge.

[OskarStark]

Suggested change

	Twig template:
	.. code-block:: php
	Twig template::

[OskarStark]

Suggested change

	set this to `false`.
	.. code-block:: php
	set this to `false`::

[sfmok]

@OskarStark done, but I think this #20872 needs to be merged first

[javiereguiluz]

@sfmok thanks a lot for contributing these docs!

Your contribution was perfectly correct, but we changed some things while merging. The fact that this constraint is stored in the Twig Bridge is an "implementation detail" that most users don't care about. We have other similar constraints (e.g. UniqueEntity from Doctrine Bridge) that are documented like a normal constraint, without explaining in detail that it belongs to a bridge.

So, we made some changes (see 344d8ba) to remove the new twig_bridge/ docs and move the contents to reference/constraints/Twig.rst.

Also, even if the constraint page titles only use the name of the constraint (e.g. just Json, IsNull, etc.) we decided to title the new page as Twig Constraint to avoid confusion with the pages related to Twig templating (in Google search results, in symfony.com search engine, etc.)

Thanks!

[sfmok]

@sfmok thanks a lot for contributing these docs!

Your contribution was perfectly correct, but we changed some things while merging. The fact that this constraint is stored in the Twig Bridge is an "implementation detail" that most users don't care about. We have other similar constraints (e.g. UniqueEntity from Doctrine Bridge) that are documented like a normal constraint, without explaining in detail that it belongs to a bridge.

So, we made some changes (see 344d8ba) to remove the new twig_bridge/ docs and move the contents to reference/constraints/Twig.rst.

Also, even if the constraint page titles only use the name of the constraint (e.g. just Json, IsNull, etc.) we decided to title the new page as Twig Constraint to avoid confusion with the pages related to Twig templating (in Google search results, in symfony.com search engine, etc.)

Thanks!

Got it, that makes perfect sense. Thanks!