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

Appearance settings

Commit 5bf67b8

Browse filesBrowse files
committed
Merge branch '4.4'
* 4.4: Remove duplicate namespace in code example Use correct code-block Remove space before self closing XML tag Remove duplicate word
2 parents 766aa0b + a97d940 commit 5bf67b8
Copy full SHA for 5bf67b8

File tree

Expand file treeCollapse file tree

3 files changed

+3
-4
lines changed
Filter options
Expand file treeCollapse file tree

3 files changed

+3
-4
lines changed

‎forms.rst

Copy file name to clipboardExpand all lines: forms.rst
+1-1Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -545,7 +545,7 @@ Form Type Options
545545

546546
Each :ref:`form type <form-types>` has a number of options to configure it, as
547547
explained in the :doc:`Symfony form types reference </reference/forms/types>`.
548-
Two commonly used options options are ``required`` and ``label``.
548+
Two commonly used options are ``required`` and ``label``.
549549

550550
The ``required`` Option
551551
.......................

‎routing.rst

Copy file name to clipboardExpand all lines: routing.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -200,7 +200,7 @@ Use the ``methods`` option to restrict the verbs each route should respond to:
200200

201201
HTML forms only support ``GET`` and ``POST`` methods. If you're calling a
202202
route with a different method from an HTML form, add a hidden field called
203-
``_method`` with the method to use (e.g. ``<input type="hidden" name="_method" value="PUT" />``).
203+
``_method`` with the method to use (e.g. ``<input type="hidden" name="_method" value="PUT"/>``).
204204
If you create your forms with :doc:`Symfony Forms </forms>` this is done
205205
automatically for you.
206206

@@ -1905,7 +1905,7 @@ Generating URLs in Templates
19051905
The Twig template language used in :doc:`Symfony templates </templating>`
19061906
provides some functions to generate both relative and absolute URLs:
19071907

1908-
.. code-block:: twig
1908+
.. code-block:: html+twig
19091909

19101910
{# generates relative URLs #}
19111911
<a href="{{ path('sign_up') }}">Sign up</a>

‎workflow.rst

Copy file name to clipboardExpand all lines: workflow.rst
-1Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -656,7 +656,6 @@ Then you can access this metadata in your controller as follows::
656656

657657
use App\Entity\BlogPost;
658658
use Symfony\Component\Workflow\Registry;
659-
use App\Entity\BlogPost;
660659

661660
public function myController(Registry $registry, BlogPost $post)
662661
{

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.