-
-
Notifications
You must be signed in to change notification settings - Fork 5.2k
[TwigBridge][Validator] Add the Twig constraint and its validator #20836
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.
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
Labels
Milestone
Comments
Thanks @fabpot, I will add the doc |
sfmok
added a commit
to sfmok/symfony-docs
that referenced
this issue
Apr 6, 2025
sfmok
added a commit
to sfmok/symfony-docs
that referenced
this issue
Apr 8, 2025
sfmok
added a commit
to sfmok/symfony-docs
that referenced
this issue
Apr 8, 2025
javiereguiluz
added a commit
that referenced
this issue
Apr 10, 2025
…fmok) This PR was merged into the 7.3 branch. Discussion ---------- [Validator] Add docs for bridge twig validator #20836 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](#20836) Related PR: [Symfony PR #58805](symfony/symfony#58805) – Introduced the Twig validator constraint in the Twig Bridge. Commits ------- ac9e20c Add docs for bridge twig validator #20836
@fabpot @javiereguiluz I think this issue can be closed as it has been resolved |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We created this issue to not forget to document this new feature. We would really appreciate if you can help us with this task. If you are not sure how to do it, please ask us and we will help you.
To fix this issue, please create a PR against the 7.3 branch in the symfony-docs repository.
Thank you! 😃
The text was updated successfully, but these errors were encountered: