@@ -230,7 +230,7 @@ controller::
230
230
}
231
231
232
232
.. versionadded :: 2.3
233
- The :method: `Symfony\C omponent\F orm\F ormInterface::handleRequest ` method was
233
+ The :method: `Symfony\\ Component\\ Form\ \ FormInterface::handleRequest ` method was
234
234
added in Symfony 2.3. Previously, the ``$request `` was passed to the
235
235
``submit `` method - a strategy which is deprecated and will be removed
236
236
in Symfony 3.0. For details on that method, see :ref: `cookbook-form-submit-request `.
@@ -239,26 +239,26 @@ This controller follows a common pattern for handling forms, and has three
239
239
possible paths:
240
240
241
241
#. When initially loading the page in a browser, the form is simply created and
242
- rendered. :method: `Symfony\C omponent\F orm\F ormInterface::handleRequest `
242
+ rendered. :method: `Symfony\\ Component\\ Form\ \ FormInterface::handleRequest `
243
243
recognizes that the form was not submitted and does nothing.
244
- :method: `Symfony\C omponent\F orm\F ormInterface::isValid ` returns ``false ``
244
+ :method: `Symfony\\ Component\\ Form\ \ FormInterface::isValid ` returns ``false ``
245
245
if the form was not submitted.
246
246
247
- #. When the user submits the form, :method: `Symfony\C omponent\F orm\F ormInterface::handleRequest `
247
+ #. When the user submits the form, :method: `Symfony\\ Component\\ Form\ \ FormInterface::handleRequest `
248
248
recognizes this and immediately writes the submitted data back into the
249
249
``task `` and ``dueDate `` properties of the ``$task `` object. Then this object
250
250
is validated. If it is invalid (validation is covered in the next section),
251
- :method: `Symfony\C omponent\F orm\F ormInterface::isValid ` returns ``false ``
251
+ :method: `Symfony\\ Component\\ Form\ \ FormInterface::isValid ` returns ``false ``
252
252
again, so the form is rendered together with all validation errors;
253
253
254
254
.. note ::
255
255
256
- You can use the method :method: `Symfony\C omponent\F orm\F ormInterface::isSubmitted `
256
+ You can use the method :method: `Symfony\\ Component\\ Form\ \ FormInterface::isSubmitted `
257
257
to check whether a form was submitted, regardless of whether or not the
258
258
submitted data is actually valid.
259
259
260
260
#. When the user submits the form with valid data, the submitted data is again
261
- written into the form, but this time :method: `Symfony\C omponent\F orm\F ormInterface::isValid `
261
+ written into the form, but this time :method: `Symfony\\ Component\\ Form\ \ FormInterface::isValid `
262
262
returns ``true ``. Now you have the opportunity to perform some actions using
263
263
the ``$task `` object (e.g. persisting it to the database) before redirecting
264
264
the user to some other page (e.g. a "thank you" or "success" page).
0 commit comments