Yonel Ceruto

As temporal, ugly workaround, you can add the new options this way (this should be done before submitting the form): ```php \Closure::bind(function () { // add here the new options...

Over there, there should be other special use cases, such as using API payloads against forms where the choice lists are not really necessary, so people work around with custom...

@stof certainly there's additional work required to create a fully-autocomplete type, which is not the goal of this PR btw. However, it does streamline implementations that previously needed custom/complex solutions....

Indeed, it's a feature added in 6.2: ``` framework: handle_all_throwables: true ``` Closing as completed.

In this case, the null value is probably related to the data bound to the form. If you don't pass any value, it is null by default, and then the...

This is not a bug.

@mtarld I like the goal of this new component and all its features, great work! However, I do believe it's too heavy for reviewers and too easy to overlook any...

Perhaps it could fit into a `symfony/functions` package or similar? On the other hand, it could fit as a Symfony component (`symfony/byte`) if we add more functionalities/classes to it, like...

The exception was suggested during implementation because the model_type = integer will work only when the divisor is different from 1. Not setting it properly will cause confusion for developers...

>I'm not sure this extra_lazy option in the existing type extending ChoiceType is the right option. Such autocomplete type requires a totally different rendering than a choice type (and this...