@@ -42,9 +42,6 @@ submissions::
42
42
Calling Form::submit() manually
43
43
-------------------------------
44
44
45
- .. versionadded :: 2.3
46
- Before Symfony 2.3, the ``submit() `` method was known as ``bind() ``.
47
-
48
45
In some cases, you want better control over when exactly your form is submitted
49
46
and what data is passed to it. Instead of using the
50
47
:method: `Symfony\\ Component\\ Form\\ FormInterface::handleRequest `
@@ -88,9 +85,16 @@ method, pass the submitted data directly to
88
85
89
86
When submitting a form via a "PATCH" request, you may want to update only a few
90
87
submitted fields. To achieve this, you may pass an optional second boolean
91
- parameter to ``submit() ``. Passing ``false `` will remove any missing fields
88
+ argument to ``submit() ``. Passing ``false `` will remove any missing fields
92
89
within the form object. Otherwise, the missing fields will be set to ``null ``.
93
90
91
+ .. caution ::
92
+
93
+ When the second parameter ``$clearMissing `` is ``false ``, like with "PATCH"
94
+ method, the validation extension will only handle the submitted fields, if
95
+ the underlying data needs to be validated, this should be done manually,
96
+ i.e using the validator.
97
+
94
98
.. _form-submit-request :
95
99
96
100
Passing a Request to Form::submit() (Deprecated)
@@ -129,5 +133,5 @@ a convenient shortcut to the previous example::
129
133
130
134
Passing the :class: `Symfony\\ Component\\ HttpFoundation\\ Request ` directly to
131
135
:method: `Symfony\\ Component\\ Form\\ FormInterface::submit ` still works, but is
132
- deprecated and will be removed in Symfony 3.0. You should use the method
136
+ deprecated and has been removed in Symfony 3.0. You should use the method
133
137
:method: `Symfony\\ Component\\ Form\\ FormInterface::handleRequest ` instead.
0 commit comments