Validación en tiempo real y campos de formulario dependientes

Has the bug mentioned at 9:25 been resolved? That use case is exactly what I'm currently trying to achieve and could have used some guidance.

Hey Ryan. Thanks again for another great tutorial. I just updated an app with a lot of form events, Ajax calls, and custom stimulus controllers, because of many dependent form fields and many kind of complex CollectionType fields.
Now I got rid of a lot of boilerplate code, and I am very happy to use LiveComponents more in the future.
For me, as a more backend-focused full-stack developer, it is a very nice technology. And now we even got to choose between multiple technologies that do in this direction (live-components, turbo, htmx as the most prominent ones).

I am just left with one question.
I am using live-components in combination with "SymfonyCasts/dynamic-forms" and it works perfect. But with my old custom setup, I knew exactly when I dynamically added dependent form fields or added/removed new items of a CollectionType, and in these cases manually added css classes to animate the newly added items/rows, so that it is smoother from a ux perspective.

How can I react to new dependent rows/fields of my form that get added or removed, or the same for items of my LiveCollection?
I know (from the awesome docs) there are hooks like "render:finished" which I am already using to get the Trix editor working with live components, but I am not sure what is the best ans most easy way to detect newly added or removed items and to add my css classes to those. Any ideas?

Hi everyone, a great tool for dependent form fields - I'm thrilled :)

I have the problem that dependent fields are no longer recognized as mandatory fields. I work with Turbo and LiveComponents. Displaying and hiding the dependent fields works wonderfully. But the "new" dependent fields are not recognized as mandatory fields if they are displayed.

Is there a solution?

thank you so much! cheers :)

Hello people form SC! I have a question on Real Time validation with Live Components. I have a form and validation is going ok. But as soon as i add a field with the DateType::class i get an error. The error occurs when i fill in an other field. But I expect that the DateTime field doesn't throw an error because i didn't changed it yet.

I tried to change the DateType field to the default values but the error keeps popping. It doesn't happen on the other required fields (nullable=false in the entity class).

The formbuilder:

            $builder
            //->add('executedAt') //The error also occurs when i change it to this field
            ->add('executedAt', type: DateType::class, options: [
                'widget' => 'single_text',
            ])
            ->add('note')
            ->add('status') //This is als a required field but when i first change the 'executedAt' field this doesn't throw an error
            ->add('attachment')
            ;
    }

The fields in the entity class:

    #[ORM\Column]
    #[Gedmo\Versioned]
    private ?\DateTimeImmutable $executedAt = null;
    
    #[ORM\Column(length: 255, nullable: true)]
    #[Gedmo\Versioned]
    private ?string $note = null;
       
    #[ORM\Column(length: 255)]
    #[Gedmo\Versioned]
    private ?string $status = null;
    
    #[ORM\Column(length: 255, nullable: true)]
    #[Gedmo\Versioned]
    private ?string $attachment = null;
    

The error:

Expected argument of type "DateTimeImmutable", "null" given at property path "executedAt".

Hi Ryan, I have a quick question on Real Time validation.

My form has a field which is a LiveCollectionType. I copied your example from the symfony ux demo page, and it works awesomely. However I'm having one weird issue with real time validation.

The validation on the embedded form type works perfectly, exactly how I would expect. However on the actual collection type, I have a constraint with a new Count(min: 1). Now, if I remove the last embedded object from the collection (or don't add any in the first place), I don't get any real time validation on this field. I can live with that, because when I post the form I will get the error displayed then. When I add to the collection, the error goes away in real time. Perfect!

But here's my issue. When this form has been posted (with zero in the collection causing the error), and now I press the 'add to collection' button, as I said the error will go away, however the embedded form is validating straight away, and since the field inside the collection is currently empty, I am getting the validation error. I would expect to NOT see a validation error until the user types something, deletes it, then tabs away. Every new embedded form added to the collection will have this issue, until the entire page is reloaded.

Did I miss something obvious?

Ryan,

I have these fields:

->add('selectedCategory', EntityType::class, [
    'class' => ItemCategories::class,
    'choice_label' => 'name',
    'placeholder' => 'Select a category',
    'required' => true,
    'label' => 'Item Categories',
])
->addDependent('selectedSubcategory', 'selectedCategory', function (DependentField $field, ?ItemCategories $category) {
        $field->add(EntityType::class, [
        'class' => ItemSubcategories::class,
        'placeholder' => null === $category ? 'Select a category first' : sprintf('Choose a category for %s', $category->getName()),
        'choices' => $category ? $category->getItemSubcategories() : [],
        'choice_label' => 'name',
        'disabled' => null === $category,
    ]);
})
->addDependent('itemGroups', 'selectedSubcategory', function (DependentField $field, ?ItemSubcategories $subcategory) {
        $field->add(EntityType::class, [
        'class' => ItemGroups::class,
        'placeholder' => null === $subcategory ? 'Select a subcategory first' : sprintf('Choose a group for %s', $subcategory->getName()),
        'choices' => $subcategory ? $subcategory->getItemGroups() : [],
        'choice_label' => 'name',
        'disabled' => null === $subcategory,
    ]);
})

All works really well on a new form, but when I render the form for an 'edit', these three fields don't have their initial data. All my other form fields do, but not these three. So one would have to re-select these fields on an edit, even if they don't want to change them. I can not figure out why, any suggestions?