Dynamic Form Events

Hi there,

here is a working example of 3 inputs based on PRE_SUBMIT events
Symfony 6, PHP 8

https://github.com/kapcus/s...

jan

Hey Jan,

Good job! Thanks for sharing this little example with other users! I think it might be useful for someone.

Cheers!

Hey.
I'm trying to do something pretty difficult (for me) with Form Component. I haven't found a solution yet so I'm sending an SOS here. I hope my explaination will be clear:

I have 2 entities with ManyToOne relation: Task and Tech. Of course, each technician could have many tasks...

In TaskType, I want to choose a technician AND if needed directly update some data about them (address, phone number). So I'm using a custom TechType and I did persist cascade from Task to Tech (and even @Assert\Valid on tech property of Task). IMO, everything is okay here.

In TechType, in addition to the classic fields (address, phone...), I have a special "name" field (TextType with autocomplete) used to CHOOSE the technician, not to update the name. After selecting a technician in the dropdown list, I'm reloading the TechType part with Ajax. Then, if needed, I can update some data in other fields.

I did many things (relatively) deep inside Form Component to create this functionality: EventListeners, DataTransformers, Underlying data... Everything seems to be OK.

BUT when submitting the form, I have an unexpected behavior: the technician is not updated but a new one is created. As I have a UniqueEntity(name) for Tech, I have a validation error "This name is already used for another technician". It seems like Doctrine is tracking a specific Tech and can't replace it with another one loaded by Ajax.

Did anyone have already done such a thing? Is there a Doctrine ID for tracking (I saw #id while dumping data to compare) ? Or maybe there's another way to do this ? If someone have an idea, it will be helpful!

Thanks a lot.
Cyril, from France.

Hey Cyril S.!

Oh boy - form events. This stuff is hard for me too :p. But wow, you've already accomplished a ton! Nice work!

I may not have the correct or best solution, bit maybe I can point you in the right direction - you seem pretty capable of figuring stuff out ;).

When you ultimately submit the form (after all the ajax fanciness), you are submitting some "task" data and also some "task[tech]" data for the technician. But, i believe that you are not actually sending the technician "id" anywhere in the POST data. I could *totally* be wrong about that part - and I hope I am. Somehow you DO need to communicate the "tech id" in the POST data somewhere. It could even be a random hidden input field that is not even part of your form. Because... in your controller, when you create the new Task() (or maybe you let the form create this object automatically - if you do, please start creating it manually), you can THEN read that POST'ed tech id value, query for the Tech object, and call $task->setTech($tech). That, I believe, will fix your problem :). Ultimately, when the form starts processing, if the Task object does not have a Tech object on it, then the TechType will automatically create one *for* you, which is why you're ultimately hitting this issue.

Let me know if this helps you solve it :).

Cheers!

Yes! It worked! You're the King, Ryan!
Thank you for your help and, once again, for your great tutorials. I'm looking forward to the next one on "Turbo".
Cyril

Hey. Why do we use the POST_SUBMIT event ? And not PRE_SUBMIT? I mean, would it not be better, to do the change before validation?

Hey Michael B.!

That's an excellent question :). So... the true answer is... I don't know. Or, at least, I don't remember. This stuff is SO complex (one of my least favorite parts of Symfony) and I can't remember all the effects of the events. But, it's definitely worth a try. You would need to get the submitting data in a different way (it's passed to the event), but that shouldn't be a problem. There is also a SUBMIT event as well, which is in the middle.

And, about validation, I can't remember if that was something I had checked into or not. As I'm guessing you already know, validation is performed on a listener to POST_SUBMIT. But is that called before our listener or after? I don't remember. As it's written, but have a priority of 0. Anyways, if your code *were* being called after validation, we could change the priority on our event listener to guarantee it comes first.

So... that's a bunch of wishy-washy answers :P. But I hope it helps.

Cheers!

Hey weaverryan .

Yes, the form component is and always has been one of the most complicated things about Symfony.

In the last year I did a lot with the JAM stack and dealt with Laravel (wrote 2 packages). At Laravel in particular, it was the first thing that struck me - how super easy it is to validate forms there. Totally painless.

On the other hand, one of Symfony's strengths is that everything is a piece and everything interlocks. I have also implemented very complex forms with Symfony. Timetables for schools, for example, everything is possible if you work your way into it.

Anyway. I think all the other technologies are cool, but now, having looked elsewhere, I come back to Symfony and will stay. You have to choose. I've been around too long and there are many areas where I just like Symfony a lot better.

I would also like to write more about Symfony in the future and help spread the framework. Because I have the feeling that it doesn't look good for the future if nobody does that. The Laravel community is much more active. And new developers are more likely to use Laravel at the moment, because it is simply much more present.

Hi,

I was coding my custom application along with your videos. I wanted to clean up my PersonFormType so I transfered EventListeners into separate "Listener" file. (like the ones from ArticleFormType in you videos)

Now I am getting this error which I cannot resolve. Can you help?
Code is exactly the same as in you videos.

Argument 1 passed to App\EventSubscriber\NumberTypeByCitizenshipSubscriber::setupNumberField() must implement interface Symfony\Component\Form\FormInterface, null given, called in C:\WAMP\www\blablabla\src\EventSubscriber\NumberTypeByCitizenshipSubscriber.php on line 43

PersonFormType.php
https://pastebin.com/W0krQjyG

NumberTypeByCitizenshipSubscriber.php
https://pastebin.com/gCcfKbXw

Thank you!

Hey SentinelBL,

It looks like that somewhere in your code where you call that "setupNumberField()" method you passes a null instead of a form object. Why? That's the correct question! Please, try to debug your code, basically you can add "dd($form)" before calling that setupNumberField() in all places and see in which cases it's null. It should give you some clue about what's going on.

I hope this helps!

Cheers!

Hi,
it's possible to do that for 3 feld?
Example: I had Country, City and Partner
City depends on Country and Partner depends on City

Hey aosow!

I don't see why not! You will just need to add a new event listener to this new dynamic form field and repeat the process feeding into your City field. Let us know if you find any unforeseen difficulties in doing this!

cityRepo = $cityRepo;
    }

    /**
     * Configuration de base d'un champ (cc: champ configuration)
     * 
     * 
     */
    private function cc($label, $placeholder, $class, $options = [])
    {
        return array_merge([
            'label' => $label,
            'attr'  => [
                'placeholder' => $placeholder,
                'class' => $class
            ]
        ], $options);
    }

    public function buildForm(FormBuilderInterface $builder, array $options)
    {
        $builder
            ->add('amount', TextType::class, $this->cc("Montant à envoyer *", "", ""))
            ->add('withdrawalAmount', TextType::class, $this->cc("Montant à recevoir *", "", ""))
            ->add('fees', TextType::class, $this->cc("Frais *", "", ""))
            ->add('total', TextType::class, $this->cc("Total à payer *", "", ""))
            ->add('paymentCurrency', ChoiceType::class, [
                'choices'  => [
                    'EUR'      => 'EUR',
                    'USD'      => 'USD',
                    'CAD'      => 'CAD',
                    'XOF'      => 'XOF'
                ],
                'label' => 'Monnaie depart *'
            ])
            ->add('recipient', EntityType::class, [
                'class' => Recipient::class,
                'choice_label' => function ($recipient) {
                    return $recipient->getFirstname() . ' ' . $recipient->getLastname();
                },
                'label' => 'Destinataire',
                'placeholder' => 'Selectionner un bénéficiare',
            ])
            ->add('withdrawalType', ChoiceType::class, [
                'choices'  => [
                    'Retrait en espèces'      => 'Retrait en espèces',
                    'Virement bancaire'      => 'Virement bancaire',
                    'MTN Mobile Money'      => 'MTN Mobile Money',
                    'Orange Money'      => 'Orange Money'
                ],
                'label' => 'Type de retrait*',
            ])
            ->add('country', EntityType::class, [
                'class' => Country::class,
                'query_builder' => function (EntityRepository $er) {
                    return $er->createQueryBuilder('c')
                        ->where('c.isAvailable = :val')
                        ->setParameter('val', true)
                        ->orderBy('c.id', 'ASC');
                },
                'choice_label' => function ($country) {
                    return Countries::getName($country->getName(), 'fr');
                },
                'label' => 'Pays d\'établissement',
                'placeholder' => 'Selectionner un pays',
            ])
        ;

        $this->handleCity($builder);
        $this->handlePartner($builder);
    }

    private function handleCity(FormBuilderInterface $builder)
    {
        $formAddCity = function (FormInterface $form, Country $country = null) {

            $cities = null === $country ? [] : $country->getCities();

            $form->add('city', EntityType::class, [
                'class' => 'App\Entity\City',
                'placeholder' => 'Selectionner la ville',
                'choices' => $cities,
                'choice_label' => 'name',
            ]);
        };

        $builder->addEventListener(
            FormEvents::PRE_SET_DATA,
            function (FormEvent $event) use ($formAddCity) {

                $transfert = $event->getData();

                $formAddCity($event->getForm(), $transfert->getCountry());
            }
        );

        $builder->get('country')->addEventListener(
            FormEvents::POST_SUBMIT,
            function (FormEvent $event) use ($formAddCity) {

                $country = $event->getForm()->getData();

                $formAddCity($event->getForm()->getParent(), $country);
            }
        );
    }

    private function handlePartner(FormBuilderInterface $builder)
    {
        $formAddPartner = function (FormInterface $form, City $city = null) {

            $partners = null === $city ? [] : $city->getPartners();

            $form->add('partner', EntityType::class, [
                'class' => 'App\Entity\Partner',
                'placeholder' => 'Selectionner un point retrait',
                'choices' => $partners,
                'choice_label' => 'comercialMane',
            ]);
        };

        $builder->addEventListener(
            FormEvents::PRE_SET_DATA,
            function (FormEvent $event) use ($formAddPartner) {

                $transfert = $event->getData();

                $formAddPartner($event->getForm(), $transfert->getCity());
            }
        );

        $builder->get('city')->addEventListener(
            FormEvents::POST_SUBMIT,
            function (FormEvent $event) use ($formAddPartner) {

                $city = $event->getForm()->getData();

                $formAddPartner($event->getForm()->getParent(), $city);
            }
        );
    }

    public function configureOptions(OptionsResolver $resolver)
    {
        $resolver->setDefaults([
            'data_class' => Transfert::class,
        ]);
    }
}

it's doesn't work

Hi this is what i tried to do but it doesn't work
cityRepo = $cityRepo;
}

/**
* Configuration de base d'un champ (cc: champ configuration)
*
*
*/
private function cc($label, $placeholder, $class, $options = [])
{
return array_merge([
'label' => $label,
'attr' => [
'placeholder' => $placeholder,
'class' => $class

]
], $options);
}

public function buildForm(FormBuilderInterface $builder, array $options)
{
$builder
->add('amount', TextType::class, $this->cc("Montant à envoyer *", "", ""))
->add('withdrawalAmount', TextType::class, $this->cc("Montant à recevoir *", "", ""))
->add('fees', TextType::class, $this->cc("Frais *", "", ""))
->add('total', TextType::class, $this->cc("Total à payer *", "", ""))
->add('paymentCurrency', ChoiceType::class, [
'choices' => [
'EUR' => 'EUR',
'USD' => 'USD',
'CAD' => 'CAD',
'XOF' => 'XOF'
],
'label' => 'Monnaie depart *'
])
->add('recipient', EntityType::class, [
'class' => Recipient::class,
'choice_label' => function ($recipient) {
return $recipient->getFirstname() . ' ' . $recipient->getLastname();
},
'label' => 'Destinataire',
'placeholder' => 'Selectionner un bénéficiare',
])
->add('withdrawalType', ChoiceType::class, [
'choices' => [
'Retrait en espèces' => 'Retrait en espèces',
'Virement bancaire' => 'Virement bancaire',
'MTN Mobile Money' => 'MTN Mobile Money',
'Orange Money' => 'Orange Money'
],
'label' => 'Type de retrait*',
])
->add('country', EntityType::class, [
'class' => Country::class,
'query_builder' => function (EntityRepository $er) {
return $er->createQueryBuilder('c')
->where('c.isAvailable = :val')
->setParameter('val', true)
->orderBy('c.id', 'ASC');
},
'choice_label' => function ($country) {
return Countries::getName($country->getName(), 'fr');
},
'label' => 'Pays d\'établissement',
'placeholder' => 'Selectionner un pays',
])
;

$this->handleCity($builder);
$this->handlePartner($builder);

}

private function handleCity(FormBuilderInterface $builder)
{

$formAddCity = function (FormInterface $form, Country $country = null) {

$cities = null === $country ? [] : $country->getCities();

$form->add('city', EntityType::class, [
'class' => 'App\Entity\City',
'placeholder' => 'Selectionner la ville',
'choices' => $cities,
'choice_label' => 'name',
]);

};

$builder->addEventListener(
FormEvents::PRE_SET_DATA,
function (FormEvent $event) use ($formAddCity) {

$transfert = $event->getData();

$formAddCity($event->getForm(), $transfert->getCountry());
}
);

$builder->get('country')->addEventListener(
FormEvents::POST_SUBMIT,
function (FormEvent $event) use ($formAddCity) {

$country = $event->getForm()->getData();

$formAddCity($event->getForm()->getParent(), $country);
}
);

}

private function handlePartner(FormBuilderInterface $builder)
{

$formAddPartner = function (FormInterface $form, City $city = null) {

$partners = null === $city ? [] : $city->getPartners();

$form->add('partner', EntityType::class, [
'class' => 'App\Entity\Partner',
'placeholder' => 'Selectionner un point retrait',
'choices' => $partners,
'choice_label' => 'comercialMane',
]);
};

$builder->addEventListener(
FormEvents::PRE_SET_DATA,
function (FormEvent $event) use ($formAddPartner) {

$transfert = $event->getData();

$formAddPartner($event->getForm(), $transfert->getCity());
}
);

$builder->get('city')->addEventListener(
FormEvents::POST_SUBMIT,
function (FormEvent $event) use ($formAddPartner) {

$city = $event->getForm()->getData();

$formAddPartner($event->getForm()->getParent(), $city);
}
);
}

public function configureOptions(OptionsResolver $resolver)
{
$resolver->setDefaults([
'data_class' => Transfert::class,
]);
}
}

Hey @aosow!

Sorry for the slow reply! This got escalated to me because... this stuff is *super* complex (one of my least favorite things to do inside of Symfony, tbh) and it's been a crazy week here :).

Anyways, are you still having the issue? If so, with the above code, what is the behavior you're seeing? Are you getting an error? Is one of the fields not being added? Is it not being added with the correct options? Does it seem to work, but you get a validation error when you submit?

Let me know!

Cheers!

Is it possible to remove children of a collection inside an event listener? I ran a little experiment and it doesn't seem possible.

Say I create a form that has one field 'deck' which is a collection of 'cards'. For testing, I manually add two cards when I create the form. Then I added this PRE_SUBMIT event listener to my form:

$form = $event->getForm();
$form->get('deck')->remove(0);
dump($form);

All is good according to the debug output. I have a form with a 'deck' collection that contains exactly one 'card' (which had 2 prior to this event). However, head on over to the controller and all is not well. Here a snippet of the controller:

$form->handleRequest($form);
dump($form);

That last dump shows two cards in the deck! What the...? Seems like shenanigans from handleRequest! So is it not possible to remove children from the form or am I doing something wrong?

Hey Christopher

You have a tiny error in the way you're trying to remove a form field. Just do this instead $form->remove('deck);
if that doesn't work, then double-check that hook into the event correctly (dump something inside your event listener function)

Cheers!

I got this working with two important changes:
1. I also had to remove the data associated with the card I was removing from the form.
2. I had to take logic for removing the form fields and data out of the event listener and instead put it in an event subscriber. I then added the event subscriber to the 'deck' field of the form. Now I can successfully remove cards and that removal survives handlRequest.

Can you shed some light on why this doesn't work in the event listener but it does work in the event subscriber? Is there a video on this topic that might help?

Hey @CMarcus!

I wish I could explain that, but I can’t :). Event listeners and subscribers are *identical* in how they work: they are *nothing* more than different ways to register which event you want to listen to. But ultimately, you are called in the same way.

So... my guess might be (because this is easy to do with forms) that maybe you attached the event listener and subscriber to slightly different parts of the form / fields. Or, in theory (though this seems unlikely), the listener vs subscriber caused your code to be called at a slightly different time due to the priority that it was registered. But I’m *really* reaching for this :).

Anyways, this stuff is hard. I still need to sit and think hard about how to solve these situations. Subtle changes (as you’ve seen) do make a difference. So, while I can’t fully explain it, nice job getting it working.

Cheers!

Thanks for the response, Diego. I was not clear in my intent here. I actually don't want to remove 'deck'. Deck is a collection of two cards and I want to remove one of the cards.

To give further details, 'deck' is a collection of CardType forms. The CardType form actually doesn't contain any fields until two fields get added in a PRE_SET_DATA event listener of CardType. In that event listener, a selection (checkbox) field is added along with an order field. In the DeckType form, the 'deck' collection of CardType forms is added as well as PRE_SUBMIT event listener where it iterates over each item in the collection and if the selection box is not checked, it attempts to remove that card. This removal of that card appears to work - if I dump the form as the last step of the PRE_SUBMIT event listener, I see that the card has been removed. But when I dump the form after returning from handleRequest in the controller, the card has been added back!

Also, DeckType does not have a data class. I haven't yet figured out if that's at play here or not.

One last point that may clarify things, I'm not attempting to remove cards from the collection that have already been persisted.

Hello everyone!

I have a question about dynamic forms.
I want to allow user to select some things that require three select inputs at all. But it must work like:
- user see one select input, he pick one value,
- js use ajax to submit data and load second select input and show it to a user with items that required data from the first select (this is the stage that works well for me using POST_SUBMIT listener)
- user pick value from second select input and now again js should submit data from select 1. and 2. and should load and show third select input that require data from 1. and 2.
And here is the problem. I have tried to use POST_SUBMIT again like this:

if ($builder->has('process')) {
    $builder->get('process')->addEventListener(
        FormEvents::POST_SUBMIT,
        static function (FormEvent $event) use ($machiningOperationFormModifier) {
            // $machiningOperationFormModifier is just closure that add new field to the form
            $process = $event->getForm()->getData(); // this is the value from 'second' select
            $frameworkProcess = $event->getForm()->getParent()->getData(); // this is the value from 'first' select
            $machiningOperationFormModifier($event->getForm()->getParent()->getParent(), $process, $frameworkProcess);
        }
    );
}

but above code is never entered by php (I have dumped).

Is it possible to make such complicated form for working well?

Hey igor_wnek!

Oh boy! These dynamic forms can be *complex*. First, I really don't know why it's not working for you. My guess is that, because you're adding the 2nd field (process) in POST_SUBMIT, when you try to look for that 2nd field, it doesn't *appear* to be there. That's just a wild guess based on what you're telling me :/.

One possible workaround is to *always* have the three fields (including process), just make the 2nd and 3rd empty (and hidden via JS) until you're reading to show them. Then, $builder->has(process') might return true. Or, it might just create more problems 🙃

Another fix might be to *always* add this POST_SUBMIT listener - do NOT bit it in an if statement. Instead, put the if statement INSIDE of the callback - e.g. $event->getForm->has('process'). That might be enough to fix things.

Good luck and let me know how it goes!

Cheers!

What about changing same field?
I have EntityType field rendered as select, which is intentionally empty on start. Then I'm using select2 to populate it with one option.
Next - in EventListener I'm changing choices list - to just one - the same that was sent from select on form submit.

And problems start here.

After populating choices with one option - Invalid value error dissapear, but 'This value should not be blank' firing.

private function setupManagerField(FormInterface $form, ?int $manager)
{
    $choices = $this->userRepository->findBy(['id' => $manager]);
    $form->add('manager', EntityType::class, [
        'class' => User::class,
        'choice_label' => function (User $user) {
            return sprintf('%s (%s)', $user->getFirstName(), $user->getUsername());
        },
        'choices' => $choices,
        'attr' => ['class' => 'select2-dropdown']
    ]);

    $form->get('manager')->setData($this->userRepository->find($manager));
}

Am I doing something wrong or this is not possible?

Hey Krzysztof K.!

Hmm, I'm not sure - this stuff is so complex - it's very easy to get some little detail wrong :/. Can you tell me more about the "why" behind what you're building? Like why there is a drop-down field with one item that is filled in dynamically with JS? I don't know the exact reasons behind what you're doing, but one other way to accomplish this (since it's not a "true" drop-down - you are always just populating it for the user with one option) is to make manager a HiddenType field. On the front-end, you an show a select visually, of course, but behind the scenes, you will truly be setting the id onto the value of that hidden field. Then, the only magic you'll need on submit is a custom data transformer on that field which will transform from the Manager object to its id and its id back to the Manager object. The whole thing might give you less trouble :).

Cheers!

The "why"

I have about 1000 users in my database. I've used select2 before and started to using it also in this case. I can't load every user to select (there are so many) on form initialization, so I came up with this solution (maybe it is crazy, but seems to me to be the most obvious one).
I have a form for project. Each project has relation to manager (User) which is required field (verified by Assert\NotBlank() in Entity). So I choose EntityType. On "new" form I initialize empty (only with placeholder) field "manager", then it is populated by select2 with Ajax with one, selected option.
Then - with no event listener - validator throws error 'invalid value' (which is pretty obvious - choices option on initialization was empty - so there is no valid values).

I came up with idea that I use EventListener to populate choices on *_SUBMIT event. I'm getting event value for manager, then querying for option with UserRepository and bringing choices to field with setupManagerField function.
Now validator throws 'empty value error'. Choices are populated by one item on form render, profiler shows that submitted value exist, but still - empty value error.

Hey Krzysztof K.!

That's not crazy at all - it's the most popular reason that you need to get into all this "form events" mess :). What's curious is that (really) you're doing the *exact* same thing I'm doing in this tutorial - you're pre-populating the "correct" choice(s) for a drop-down menu on submit so that you do not get the "This value is not valid" from the field. The only big difference is that I'm using ChoiceType and you're using EntityType - but these are effectively the same thing.

So, you're getting the:

> This value should not be blank

validation error. I can suggest 2 things:

1) Check out the profiler for your form AFTER the submit (so when you're looking at the page with the validation error) - specifically look at the part of the form profiler for your "manager" field. What does the "submitted data" say for that field? It *seems* like the field thinks that there is *no* submitted data. I would also be interested in what dump($form['manager']->getData()) looks like after "handling the form" inside your controller. Is that null?

2) Or... you can just try a different strategy :p. What you're doing is certainly not a wrong strategy. But since you are not *truly* ever using the "drop down" functionality of the EntityType, I would probably have done this initially as a "hidden" input field (which select2 populates) and then used a custom data transformer to go from entity -> id and id -> entity. The downside is that you're not re-using the built-in "entity transformation" that EntityType gives you... but the positive is that dealing with a "hidden" input field is simpler: no need to mess around with events. In your data transformer, you would simply need to take the submitted "id" and query for a manager object. If there was some restriction where only some users can be selected as "managers" and a "bad" user hacked the HTML and submitted a manager id that should *not* be used, simply detect that in your data tranformer.

Let me know what you do and how it goes!

Cheers!

This is real crazyness :) I dont get how do know when we need builder, and when we need form object. For example $builder->get('location') why not $form->get('location') ? :) and isnt this one of example of when to not use symfony form ?:)

Hey Lijana Z.

Haha, yes, this is madness, and yes, in this situation you may want to use something different than Symfony Forms. About the differences between the FormBuilder and FormInterface is that the FormBuilder is who creates instances of FormInterfaces. So, when you are inside a FormType, you will be working with a FormBuilder instance. In this case the method setupSpecificLocationNameField() is called inside an EventForm, and that event gets called after the building time, that's why you have to work directly with a FormInterface instance. I hope I didn't leave you more confused than you actually were :p

Cheers!

I think its more clear, thanks :) Not sure if I remember when I need it :D

It should be easy, whenever you feel like it's just so complex, you should use something else :)
Tools are for making our job easier not harder

Cheers!

yes, I also think, that tools should do job easier, not harder. But maybe sometimes its harder because you dont know tool well. Otherwise, for me it looks like using symfony framework should not be an option :) when I worked with codeigniter and laravel 4, it felt much easier than symfony :) But maybe if I would not use things like forms and other features, then it could be similar to laravel by dificulty.

> But maybe sometimes its harder because you dont know tool well

That's so true, not knowing how a tool works makes things harder but it should only happen in the beginning, as you keep working with it, you get more proficient, and you should feel the benefits of using the tool

Hello !
I'm struggling with a form that has both a dynamic field1 (depending on the connected user) for which I use
$builder->addEventListener(FormEvents::PRE_SET_DATA [...]
and a field2 that depends on the value selected in field1 like the example of this page.
How can I handle that ?

Hey Nicoschwartz,

Take a look at the next chapter: https://symfonycasts.com/sc... - I think it might help you to implement this.

Cheers!

Thank you but I think I might have missed something.
When I try to do $builder->get('field1')->addEventListener(...)
I get an error The child with the name "field1" does not exist.since it is only added with the EventListener $builder->addEventListener(FormEvents::PRE_SET_DATA [...]{

problem solved :)

Hey Nicoschwartz!

Awesome! Thank you for the feedback that you were able to solve it. If you have an extra solution that was not covered in our videos - it would be great if you were able to share it in your comment - it might help others a lot.

Also, I think this thread might me interesting for people as well: https://symfonycasts.com/sc... - just wanted to add a cross link to it.

Cheers!