Fixed code examples in cookbook/form

Author: wouterj

cookbook/form/create_custom_field_type.rst

@@ -20,7 +20,7 @@ will be called `GenderType` and the file will be stored in the default location
 for form fields, which is ``<BundleName>\Form\Type``. Make sure the field extends
 :class:`Symfony\\Component\\Form\\AbstractType`::
 
-    # src/Acme/DemoBundle/Form/Type/GenderType.php
+    // src/Acme/DemoBundle/Form/Type/GenderType.php
     namespace Acme\DemoBundle\Form\Type;
 
     use Symfony\Component\Form\AbstractType;
@@ -107,23 +107,22 @@ we want to always render it in a ``ul`` element. In your form theme template
 .. code-block:: html+jinja
 
     {# src/Acme/DemoBundle/Resources/views/Form/fields.html.twig #}
-
     {% block gender_widget %}
-    {% spaceless %}
-        {% if expanded %}
-            <ul {{ block('widget_container_attributes') }}>
-            {% for child in form %}
-                <li>
-                    {{ form_widget(child) }}
-                    {{ form_label(child) }}
-                </li>
-            {% endfor %}
-            </ul>
-        {% else %}
-            {# just let the choice widget render the select tag #}
-            {{ block('choice_widget') }}
-        {% endif %}
-    {% endspaceless %}
+        {% spaceless %}
+            {% if expanded %}
+                <ul {{ block('widget_container_attributes') }}>
+                {% for child in form %}
+                    <li>
+                        {{ form_widget(child) }}
+                        {{ form_label(child) }}
+                    </li>
+                {% endfor %}
+                </ul>
+            {% else %}
+                {# just let the choice widget render the select tag #}
+                {{ block('choice_widget') }}
+            {% endif %}
+        {% endspaceless %}
     {% endblock %}
 
 .. note::
@@ -136,7 +135,6 @@ we want to always render it in a ``ul`` element. In your form theme template
     .. code-block:: yaml
 
         # app/config/config.yml
-
         twig:
             form:
                 resources:
@@ -231,7 +229,7 @@ returned by the ``getName`` method defined earlier. We'll see the importance
 of this in a moment when we use the custom field type. But first, add a ``__construct``
 argument to ``GenderType``, which receives the gender configuration::
 
-    # src/Acme/DemoBundle/Form/Type/GenderType.php
+    // src/Acme/DemoBundle/Form/Type/GenderType.php
     namespace Acme\DemoBundle\Form\Type;
     // ...
 
@@ -276,4 +274,4 @@ Notice that instead of instantiating a new instance, we can just refer to
 it by the alias used in our service configuration, ``gender``. Have fun!
 
 .. _`ChoiceType`: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/Extension/Core/Type/ChoiceType.php
-.. _`FieldType`: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/Extension/Core/Type/FieldType.php
+.. _`FieldType`: https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Form/Extension/Core/Type/FieldType.php

cookbook/form/data_transformers.rst

@@ -101,7 +101,6 @@ was entered::
 Next, we create the data transformer, which does the actual conversion::
 
     // src/Acme/TaskBundle/Form/DataTransformer/IssueToNumberTransformer.php
-
     namespace Acme\TaskBundle\Form\DataTransformer;
 
     use Symfony\Component\Form\DataTransformerInterface;
@@ -193,7 +192,6 @@ manager can be automatically injected:
 You can now add the type to your form by its alias as follows::
 
     // src/Acme/TaskBundle/Form/Type/TaskType.php
-
     namespace Acme\TaskBundle\Form\Type;
 
     use Symfony\Component\Form\AbstractType;
@@ -206,8 +204,7 @@ You can now add the type to your form by its alias as follows::
             $builder
                 ->add('task')
                 ->add('dueDate', null, array('widget' => 'single_text'));
-                ->add('issue', 'issue_selector')
-            ;
+                ->add('issue', 'issue_selector');
         }
 
         public function getName()

cookbook/form/dynamic_form_generation.rst

@@ -7,7 +7,7 @@ How to Dynamically Generate Forms Using Form Events
 Before jumping right into dynamic form generation, let's have a quick review 
 of what a bare form class looks like::
 
-    //src/Acme/DemoBundle/Form/ProductType.php
+    // src/Acme/DemoBundle/Form/ProductType.php
     namespace Acme\DemoBundle\Form;
 
     use Symfony\Component\Form\AbstractType;
@@ -53,7 +53,7 @@ So, instead of directly adding that "name" widget via our ProductType form
 class, let's delegate the responsibility of creating that particular field 
 to an Event Subscriber::
 
-    //src/Acme/DemoBundle/Form/ProductType.php
+    // src/Acme/DemoBundle/Form/ProductType.php
     namespace Acme\DemoBundle\Form
 
     use Symfony\Component\Form\AbstractType

cookbook/form/form_collections.rst

@@ -199,6 +199,7 @@ zero tags when first created).
     .. code-block:: html+jinja
 
         {# src/Acme/TaskBundle/Resources/views/Task/new.html.twig #}
+
         {# ... #}
 
         <form action="..." method="POST" {{ form_enctype(form) }}>
@@ -220,6 +221,7 @@ zero tags when first created).
     .. code-block:: html+php
 
         <!-- src/Acme/TaskBundle/Resources/views/Task/new.html.php -->
+
         <!-- ... -->
 
         <form action="..." method="POST" ...>
@@ -279,6 +281,7 @@ type expects to receive exactly two, otherwise an error will be thrown:
 add the ``allow_add`` option to our collection field::
 
     // src/Acme/TaskBundle/Form/Type/TaskType.php
+
     // ...
     
     public function buildForm(FormBuilder $builder, array $options)
@@ -307,7 +310,7 @@ new "tag" forms. To render it, make the following change to your template:
 
     .. code-block:: html+jinja
 
-        <ul class="tags" data-prototype="{{ form_widget(form.tags.vars.prototype) | e }}">
+        <ul class="tags" data-prototype="{{ form_widget(form.tags.vars.prototype)|e }}">
             ...
         </ul>
 
@@ -333,7 +336,7 @@ new "tag" forms. To render it, make the following change to your template:
 
     .. code-block:: html+jinja
 
-        {{ form_widget(form.tags.vars.prototype.name) | e }}
+        {{ form_widget(form.tags.vars.prototype.name)|e }}
 
 On the rendered page, the result will look something like this:
 
@@ -424,6 +427,10 @@ new ``Tag`` objects and added to the ``tags`` property of the ``Task`` object.
 
         .. code-block:: php-annotations
 
+            // src/Acme/TaskBundle/Entity/Task.php
+
+            // ...
+
             /**
              * @ORM\ManyToMany(targetEntity="Tag", cascade={"persist"})
              */
@@ -453,6 +460,7 @@ new ``Tag`` objects and added to the ``tags`` property of the ``Task`` object.
     is set to ``false``::
     
         // src/Acme/TaskBundle/Entity/Task.php
+
         // ...
 
         public function setTags(ArrayCollection $tags)
@@ -467,6 +475,7 @@ new ``Tag`` objects and added to the ``tags`` property of the ``Task`` object.
     Inside ``Tag``, just make sure you have an ``addTask`` method::
 
         // src/Acme/TaskBundle/Entity/Tag.php
+
         // ...
 
         public function addTask(Task $task)
@@ -490,6 +499,7 @@ The solution is similar to allowing tags to be added.
 Start by adding the ``allow_delete`` option in the form Type::
     
     // src/Acme/TaskBundle/Form/Type/TaskType.php
+
     // ...
     
     public function buildForm(FormBuilder $builder, array $options)
@@ -573,6 +583,7 @@ the relationship between the removed ``Tag`` and ``Task`` object.
     is handling the "update" of your Task::
 
         // src/Acme/TaskBundle/Controller/TaskController.php
+
         // ...
 
         public function editAction($id, Request $request)