From dbe120598ca6fd38b38adff456a2247d3849645b Mon Sep 17 00:00:00 2001 From: Thomas Landauer Date: Sun, 12 Jun 2016 23:58:25 +0200 Subject: [PATCH] Added info on doctrine metadata implications on validation It took me a while to figure this out. So I think it should be explained *somewhere*. I'm not sure if this is the right place, and I'm also not sure if the information is comprehensive. Just wanted to get somehing going about 'Doctrine and validation' somewhere in the docs. --- book/forms.rst | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/book/forms.rst b/book/forms.rst index 7f527d42216..77528918eb6 100644 --- a/book/forms.rst +++ b/book/forms.rst @@ -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