[Form] Deprecate not configuring the "widget" option of date/time form types#49588
Conversation
html5 widget option - DateType / DateTimeType / TimeTypehtml5 widget option - DateType / DateTimeType / TimeType
html5 widget option - DateType / DateTimeType / TimeTypehtml5 widget option - DateType / DateTimeType / TimeType
html5 widget option - DateType / DateTimeType / TimeTypehtml5 widget option - DateType / DateTimeType / TimeType
|
Adding a new value for the Instead, what about deprecating not setting the |
I got your point and this sounds good to achieve the same result of simplification. |
|
We did follow a similar approach in the past. By asking ppl to be explicit in v6, we can then change the default in v7. To support many versions, one should be explicit about the behavior they want in all versions. They can do so immediately. |
Thanks for explanation |
43635bb to
67893b3
Compare
67893b3 to
04fac82
Compare
html5 widget option - DateType / DateTimeType / TimeType04fac82 to
a1e3dea
Compare
There was a problem hiding this comment.
I added a 2nd commit that updates the codebase to always set the widget option, so that we don't trigger the deprecation ourselves.
a1e3dea to
31c3db9
Compare
31c3db9 to
138be68
Compare
138be68 to
1ca33e7
Compare
|
Thank you @MrYamous. |
|
This is a breaking change btw, the combination [html5 => false, widget => single_text] is not possible anymore, widget => single_text causes html5 to be true regardless of the given option |
|
@faizanakram99 Please open a new issue. Comments on merged pull requests are likely to get lost. |
This PR proposes to change the default value of the
widgetoption of date/time form types tosingle_text, so that the corresponding input fields are rendered using native HTML5 widgets by default.It does so by deprecating not setting the
widgetoption, so that we can change the default in Symfony 7.