Skip to content

Added info on doctrine metadata implications on validation #6649

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.

Sign up for GitHub

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

Closed
wants to merge 1 commit into from
Closed

Added info on doctrine metadata implications on validation #6649

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions book/forms.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1277,6 +1277,15 @@ data is transferred to the underlying object immediately. If you want to
persist that data, you simply need to persist the object itself (which already
contains the submitted data).

Using Doctrine metadata for validation
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
If you've defined a `length` property of your Doctrine entity, a corresponding
`maxlength` attribute will be added automatically when rendering the form.
However, this only accounts for client-side validation on compatible browsers.
For true server-side validation, you still need to define corresponding rules,
as explained in :doc:`/book/validation`. Currently, it is not possible to re-use
Doctrine mapping metadata for validation directly.

.. index::
single: Forms; Embedded forms

Expand Down