Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit038da90

Browse files
patieweaverryan
authored andcommitted
fixed links to API for isValid() and handleRequest()
1 parentf8ace43 commit038da90

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

‎book/forms.rst

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -230,7 +230,7 @@ controller::
230230
}
231231

232232
..versionadded::2.3
233-
The:method:`Symfony\Component\Form\FormInterface::handleRequest` method was
233+
The:method:`Symfony\\Component\\Form\\FormInterface::handleRequest` method was
234234
added in Symfony 2.3. Previously, the ``$request`` was passed to the
235235
``submit`` method - a strategy which is deprecated and will be removed
236236
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
239239
possible paths:
240240

241241
#. When initially loading the page in a browser, the form is simply created and
242-
rendered.:method:`Symfony\Component\Form\FormInterface::handleRequest`
242+
rendered.:method:`Symfony\\Component\\Form\\FormInterface::handleRequest`
243243
recognizes that the form was not submitted and does nothing.
244-
:method:`Symfony\Component\Form\FormInterface::isValid` returns ``false``
244+
:method:`Symfony\\Component\\Form\\FormInterface::isValid` returns ``false``
245245
if the form was not submitted.
246246

247-
#. When the user submits the form,:method:`Symfony\Component\Form\FormInterface::handleRequest`
247+
#. When the user submits the form,:method:`Symfony\\Component\\Form\\FormInterface::handleRequest`
248248
recognizes this and immediately writes the submitted data back into the
249249
``task`` and ``dueDate`` properties of the ``$task`` object. Then this object
250250
is validated. If it is invalid (validation is covered in the next section),
251-
:method:`Symfony\Component\Form\FormInterface::isValid` returns ``false``
251+
:method:`Symfony\\Component\\Form\\FormInterface::isValid` returns ``false``
252252
again, so the form is rendered together with all validation errors;
253253

254254
..note::
255255

256-
You can use the method:method:`Symfony\Component\Form\FormInterface::isSubmitted`
256+
You can use the method:method:`Symfony\\Component\\Form\\FormInterface::isSubmitted`
257257
to check whether a form was submitted, regardless of whether or not the
258258
submitted data is actually valid.
259259

260260
#. When the user submits the form with valid data, the submitted data is again
261-
written into the form, but this time:method:`Symfony\Component\Form\FormInterface::isValid`
261+
written into the form, but this time:method:`Symfony\\Component\\Form\\FormInterface::isValid`
262262
returns ``true``. Now you have the opportunity to perform some actions using
263263
the ``$task`` object (e.g. persisting it to the database) before redirecting
264264
the user to some other page (e.g. a "thank you" or "success" page).

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp