Oct 16, 2017
diff --git a/best_practices/forms.rst b/best_practices/forms.rst
        // render the template
    }

 .. versionadded:: 4.1
   The ``ControllerTrait::isFormValid()`` method was added in Symfony 4.1.


 It's also possible to use a short-cut if the ``ControllerTrait`` is imported:


 .. code-block:: php

    public function newAction(Request $request)
    {
        // build the form ...

        if ($this->isFormValid($form)) {
            // process the form data
        }

        // render the template
    }

 There are really only two notable things here. First, we recommend that you
 use a single action for both rendering the form and handling the form submit.
 For example, you *could* have a ``newAction()`` that *only* renders the form
diff --git a/forms.rst b/forms.rst
    is called. Otherwise, changes done in the ``*_SUBMIT`` events aren't applied to the
    view (like validation errors).


 .. versionadded:: 4.1
   The ``ControllerTrait::isFormValid()`` method was added in Symfony 4.1.


 It's also possible to use a short-cut if the ``ControllerTrait`` is imported:


 .. code-block:: php

    public function newAction(Request $request)
    {
        // build the form ...

        if ($this->isFormValid($form)) {
            // process the form data
        }

        // render the template
    }


 This controller follows a common pattern for handling forms and has three
 possible paths:
Original file line number	Diff line number	Diff line change
Expand Up		@@ -197,6 +197,26 @@ Handling a form submit usually follows a similar template:
		// render the template
		}

		.. versionadded:: 4.1
		The ``ControllerTrait::isFormValid()`` method was added in Symfony 4.1.


		It's also possible to use a short-cut if the ``ControllerTrait`` is imported:


		.. code-block:: php

		public function newAction(Request $request)
		{
		// build the form ...

		if ($this->isFormValid($form)) {
		// process the form data
		}

		// render the template
		}

		There are really only two notable things here. First, we recommend that you
		use a single action for both rendering the form and handling the form submit.
		For example, you could have a ``newAction()`` that only renders the form
Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -259,6 +259,28 @@ your controller::
		is called. Otherwise, changes done in the ``*_SUBMIT`` events aren't applied to the
		view (like validation errors).


		.. versionadded:: 4.1
		The ``ControllerTrait::isFormValid()`` method was added in Symfony 4.1.


		It's also possible to use a short-cut if the ``ControllerTrait`` is imported:


		.. code-block:: php

		public function newAction(Request $request)
		{
		// build the form ...

		if ($this->isFormValid($form)) {
		// process the form data
		}

		// render the template
		}


		This controller follows a common pattern for handling forms and has three
		possible paths:

Expand Down