Yonel Ceruto
Yonel Ceruto
I renamed the option to `choice_lazy` and moved it to `ChoiceType` as a generic option. Now it's part of the family of `choice_*` options.
Thanks @xabbuh for your review! I also added two test cases more about `multiple` option combined with `choice_lazy`.
Just rebased to fix conflicts.
>@nicolas-grekas this lazy mode assumes that you have a form rendering that does not need the list of available choices (and so not rendering it as a `` like the...
> Maybe stupid comment: can't we always behave lazily when choice_loader is set and get rid of the option altogether? You might still want to use a `choice_loader` even without...
This is ready on my side. @stof any blocker on your side?
FYI, we are making the `config/` dir optional for 7.2 https://github.com/symfony/symfony/pull/57408
If those hooks are decorators, then the table is already set with the [Stacking decorators](https://symfony.com/doc/current/service_container/service_decoration.html#stacking-decorators) feature, applicable for all kind of services. Also, you'll be in control of the before/after...
Here is my attempt to address this issue using the Python Decorator concept: https://github.com/symfony/symfony/pull/58076 I made another attempt before this one to see if we could use the current [Proxy](https://symfony.com/doc/current/components/var_exporter.html#lazyproxytrait)...
@BeryJu does that mean we cannot authenticate on behave of a user? From what we tried, the `client_credentials` work properly with the service account + token but we are not...