@@ -84,7 +84,7 @@ objects::
84
84
85
85
Then, create a form class so that a ``Tag `` object can be modified by the user::
86
86
87
- // src/Form/Type/ TagType.php
87
+ // src/Form/TagType.php
88
88
namespace App\Form;
89
89
90
90
use App\Entity\Tag;
@@ -114,7 +114,7 @@ form itself, create a form for the ``Task`` class.
114
114
Notice that you embed a collection of ``TagType `` forms using the
115
115
:doc: `CollectionType </reference/forms/types/collection >` field::
116
116
117
- // src/Form/Type/ TaskType.php
117
+ // src/Form/TaskType.php
118
118
namespace App\Form;
119
119
120
120
use App\Entity\Task;
@@ -254,7 +254,7 @@ type expects to receive exactly two, otherwise an error will be thrown:
254
254
``This form should not contain extra fields ``. To make this flexible,
255
255
add the ``allow_add `` option to your collection field::
256
256
257
- // src/Form/Type/ TaskType.php
257
+ // src/Form/TaskType.php
258
258
259
259
// ...
260
260
use Symfony\Component\Form\FormBuilderInterface;
@@ -418,7 +418,7 @@ for the tags in the ``Task`` class::
418
418
419
419
Next, add a ``by_reference `` option to the ``tags `` field and set it to ``false ``::
420
420
421
- // src/Form/Type/ TaskType.php
421
+ // src/Form/TaskType.php
422
422
423
423
// ...
424
424
public function buildForm(FormBuilderInterface $builder, array $options)
@@ -550,7 +550,7 @@ The solution is similar to allowing tags to be added.
550
550
551
551
Start by adding the ``allow_delete `` option in the form Type::
552
552
553
- // src/Form/Type/ TaskType.php
553
+ // src/Form/TaskType.php
554
554
555
555
// ...
556
556
public function buildForm(FormBuilderInterface $builder, array $options)
0 commit comments