Jules Pietri
Jules Pietri
~What about other `Date*` types? Shouldn't this be done at the transformer level so such consistency can be checked in all of them?~ EDIT: no model transformation to hook into...
Should we create a dedicated listener that can be used in other `Date*` types as well?
Now that we have config builders we could ship both yaml and php config files in recipes, then we could use an option (i.e using composer extra) to define which...
Hello @ludekbenedik, it seems expected since the `empty_data` expects a value in the view format, in this case a repeated value like: ```php $builder->add('password', RepeatedType::class, [ 'type' => PasswordType::class, 'required'...
Hi @Silverspur, I've updated the fix in #17771, could you please confirm it works for your use case ?
Added failing test case in #17771, Status: Reviewed
Hi @mathroc, I'm actually not very happy with the [hardcoding of the filter and function](https://github.com/silexphp/Silex-WebProfiler/blob/master/WebProfilerServiceProvider.php#L204-L211) either. The `SecurityBundle` only requires `symfony/yaml` in dev but needs them to dump collected data...
Looks like you need a rebase here :)
That would be a great feature indeed. Thanks @adelgado 👍
Hello @Soonz, this should be possible indeed as there are nothing telling otherwise at http://htmlpurifier.org/live/configdoc/plain.html#URI.Munge. Maybe this issue should be opened in https://github.com/Exercise/HTMLPurifierBundle instead?