Updated form aliases to FQCNs for forms in book and component

Author: hiddewie

book/forms.rst

@@ -91,9 +91,9 @@ from inside a controller::
             $task->setDueDate(new \DateTime('tomorrow'));
 
             $form = $this->createFormBuilder($task)
-                ->add('task', 'text')
-                ->add('dueDate', 'date')
-                ->add('save', 'submit', array('label' => 'Create Task'))
+                ->add('task', 'Symfony\Component\Form\Extension\Core\Type\TextType')
+                ->add('dueDate', 'Symfony\Component\Form\Extension\Core\Type\DateType')
+                ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType', array('label' => 'Create Task'))
                 ->getForm();
 
             return $this->render('default/new.html.twig', array(
@@ -116,8 +116,20 @@ building the form.
 
 In this example, you've added two fields to your form - ``task`` and ``dueDate`` -
 corresponding to the ``task`` and ``dueDate`` properties of the ``Task`` class.
-You've also assigned each a "type" (e.g. ``text``, ``date``), which, among
-other things, determines which HTML form tag(s) is rendered for that field.
+You've also assigned each a "type" (e.g. ``TextType`` and ``DateType``),
+represented by its fully qualified class name. Among other things, it determines
+which HTML form tag(s) is rendered for that field.
+
+.. tip::
+
+   If you are using PHP 5.5 or later you can use the ``::class`` constant of a
+   form type to get its fully qualified class name. Make sure you include the
+   class with a ``use`` statement.
+
+.. versionadded:: 2.8
+    To denote the form type, you have to use the fully qualified class name.
+    Before Symfony 2.8, you could use an alias for each type like 'name' or
+    'date'.
 
 Finally, you added a submit button with a custom label for submitting the form to
 the server.
@@ -224,9 +236,9 @@ controller::
         $task = new Task();
 
         $form = $this->createFormBuilder($task)
-            ->add('task', 'text')
-            ->add('dueDate', 'date')
-            ->add('save', 'submit', array('label' => 'Create Task'))
+            ->add('task', 'Symfony\Component\Form\Extension\Core\Type\TextType')
+            ->add('dueDate', 'Symfony\Component\Form\Extension\Core\Type\DateType')
+            ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType', array('label' => 'Create Task'))
             ->getForm();
 
         $form->handleRequest($request);
@@ -241,7 +253,7 @@ controller::
             'form' => $form->createView(),
         ));
     }
-    
+
 .. caution::
 
     Be aware that the ``createView()`` method should be called *after* ``handleRequest``
@@ -310,10 +322,10 @@ which of the buttons was clicked to adapt the program flow in your controller.
 To do this, add a second button with the caption "Save and add" to your form::
 
     $form = $this->createFormBuilder($task)
-        ->add('task', 'text')
-        ->add('dueDate', 'date')
-        ->add('save', 'submit', array('label' => 'Create Task'))
-        ->add('saveAndAdd', 'submit', array('label' => 'Save and Add'))
+        ->add('task', 'Symfony\Component\Form\Extension\Core\Type\TextType')
+        ->add('dueDate', 'Symfony\Component\Form\Extension\Core\Type\DateType')
+        ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType', array('label' => 'Create Task'))
+        ->add('saveAndAdd', 'Symfony\Component\Form\Extension\Core\Type\SubmitType', array('label' => 'Save and Add'))
         ->getForm();
 
 In your controller, use the button's
@@ -622,8 +634,8 @@ First, we need to add the two buttons to the form::
 
     $form = $this->createFormBuilder($task)
         // ...
-        ->add('nextStep', 'submit')
-        ->add('previousStep', 'submit')
+        ->add('nextStep', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
+        ->add('previousStep', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
         ->getForm();
 
 Then, we configure the button for returning to the previous step to run
@@ -632,7 +644,7 @@ so we set its ``validation_groups`` option to false::
 
     $form = $this->createFormBuilder($task)
         // ...
-        ->add('previousStep', 'submit', array(
+        ->add('previousStep', 'Symfony\Component\Form\Extension\Core\Type\SubmitType', array(
             'validation_groups' => false,
         ))
         ->getForm();
@@ -701,7 +713,7 @@ the documentation for each type.
     The label for the form field can be set using the ``label`` option,
     which can be applied to any field::
 
-        ->add('dueDate', 'date', array(
+        ->add('dueDate', 'Symfony\Component\Form\Extension\Core\Type\DateType', array(
             'widget' => 'single_text',
             'label'  => 'Due Date',
         ))
@@ -722,7 +734,7 @@ Now that you've added validation metadata to the ``Task`` class, Symfony
 already knows a bit about your fields. If you allow it, Symfony can "guess"
 the type of your field and set it up for you. In this example, Symfony can
 guess from the validation rules that both the ``task`` field is a normal
-``text`` field and the ``dueDate`` field is a ``date`` field::
+``TextType`` field and the ``dueDate`` field is a ``DateType`` field::
 
     public function newAction()
     {
@@ -731,7 +743,7 @@ guess from the validation rules that both the ``task`` field is a normal
         $form = $this->createFormBuilder($task)
             ->add('task')
             ->add('dueDate', null, array('widget' => 'single_text'))
-            ->add('save', 'submit')
+            ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
             ->getForm();
     }
 
@@ -992,9 +1004,9 @@ ways. If you build your form in the controller, you can use ``setAction()`` and
     $form = $this->createFormBuilder($task)
         ->setAction($this->generateUrl('target_route'))
         ->setMethod('GET')
-        ->add('task', 'text')
-        ->add('dueDate', 'date')
-        ->add('save', 'submit')
+        ->add('task', 'Symfony\Component\Form\Extension\Core\Type\TextType')
+        ->add('dueDate', 'Symfony\Component\Form\Extension\Core\Type\DateType')
+        ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
         ->getForm();
 
 .. note::
@@ -1064,36 +1076,20 @@ that will house the logic for building the task form::
             $builder
                 ->add('task')
                 ->add('dueDate', null, array('widget' => 'single_text'))
-                ->add('save', 'submit')
+                ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
             ;
         }
-
-        public function getName()
-        {
-            return 'task';
-        }
     }
 
-.. caution::
-
-    The ``getName()`` method returns the identifier of this form "type". These
-    identifiers must be unique in the application. Unless you want to override
-    a built-in type, they should be different from the default Symfony types
-    and from any type defined by a third-party bundle installed in your application.
-    Consider prefixing your types with ``app_`` to avoid identifier collisions.
-
 This new class contains all the directions needed to create the task form. It can
 be used to quickly build a form object in the controller::
 
     // src/AppBundle/Controller/DefaultController.php
 
-    // add this new use statement at the top of the class
-    use AppBundle\Form\Type\TaskType;
-
     public function newAction()
     {
         $task = ...;
-        $form = $this->createForm(new TaskType(), $task);
+        $form = $this->createForm('AppBundle\Form\Type\TaskType', $task);
 
         // ...
     }
@@ -1160,15 +1156,47 @@ the choice is ultimately up to you.
 Defining your Forms as Services
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-Defining your form type as a service is a good practice and makes it really
-easy to use in your application.
+Your form type might have some external dependencies. You can define your form
+type as a service, and inject inject all dependencies you need.
 
 .. note::
 
     Services and the service container will be handled
     :doc:`later on in this book </book/service_container>`. Things will be
     more clear after reading that chapter.
 
+You might want to use a service defined as ``app.my_service`` in your form
+type. Create a constructor to your form type to receive the service::
+
+    // src/AppBundle/Form/Type/TaskType.php
+    namespace AppBundle\Form\Type;
+
+    use App\Utility\MyService;
+    use Symfony\Component\Form\AbstractType;
+    use Symfony\Component\Form\FormBuilderInterface;
+
+    class TaskType extends AbstractType
+    {
+        private $myService;
+
+        public function __construct(MyService $mySevice)
+        {
+            $this->myService = $myService;
+        }
+
+        public function buildForm(FormBuilderInterface $builder, array $options)
+        {
+            // You can now use myService.
+            $builder
+                ->add('task')
+                ->add('dueDate', null, array('widget' => 'single_text'))
+                ->add('save', 'Symfony\Component\Form\Extension\Core\Type\SubmitType')
+            ;
+        }
+    }
+
+Define your form type as a service.
+
 .. configuration-block::
 
     .. code-block:: yaml
@@ -1177,8 +1205,9 @@ easy to use in your application.
         services:
             app.form.type.task:
                 class: AppBundle\Form\Type\TaskType
+                arguments: ["@app.my_service"]
                 tags:
-                    - { name: form.type, alias: task }
+                    - { name: form.type }
 
     .. code-block:: xml
 
@@ -1190,52 +1219,25 @@ easy to use in your application.
 
             <services>
                 <service id="app.form.type.task" class="AppBundle\Form\Type\TaskType">
-                    <tag name="form.type" alias="task" />
+                    <argument type="service" id="app.my_service"></argument>
                 </service>
             </services>
         </container>
 
     .. code-block:: php
 
         // src/AppBundle/Resources/config/services.php
+        $definition = new Definition('AppBundle\Form\Type\TaskType', array(
+            new Reference('app.my_service'),
+        ));
         $container
-            ->register(
+            ->setDefinition(
                 'app.form.type.task',
-                'AppBundle\Form\Type\TaskType'
+                $definition
             )
-            ->addTag('form.type', array(
-                'alias' => 'task',
-            ))
+            ->addTag('form.type')
         ;
 
-That's it! Now you can use your form type directly in a controller::
-
-    // src/AppBundle/Controller/DefaultController.php
-    // ...
-
-    public function newAction()
-    {
-        $task = ...;
-        $form = $this->createForm('task', $task);
-
-        // ...
-    }
-
-or even use from within the form type of another form::
-
-    // src/AppBundle/Form/Type/ListType.php
-    // ...
-
-    class ListType extends AbstractType
-    {
-        public function buildForm(FormBuilderInterface $builder, array $options)
-        {
-            // ...
-
-            $builder->add('someTask', 'task');
-        }
-    }
-
 Read :ref:`form-cookbook-form-field-service` for more information.
 
 .. index::
@@ -1360,11 +1362,6 @@ create a form class so that a ``Category`` object can be modified by the user::
                 'data_class' => 'AppBundle\Entity\Category',
             ));
         }
-
-        public function getName()
-        {
-            return 'category';
-        }
     }
 
 The end goal is to allow the ``Category`` of a ``Task`` to be modified right
@@ -1380,7 +1377,7 @@ class:
     {
         // ...
 
-        $builder->add('category', new CategoryType());
+        $builder->add('category', 'AppBundle\Form\Type\CategoryType');
     }
 
 The fields from ``CategoryType`` can now be rendered alongside those from