Bug #103162
open
The f:form ViewHelper can not handle arrays as object attribute anymore
0%
Description
Before adding strict types in V12 the <f:form> ViewHelper could be utilized with arrays as object attribute values.
<f:form objectName="q" object="{array}">
Since V12 this will throw a TypeError because the method signature of the AbstractFormViewHelper has changed and does only allow ?object parameters, which is not consistent with the viewhelper argument type (mixed), that does not implicitly say, that arrays are not to be used.
I personally often utilize the <f:form> viewhelper with arrays to handle simple search forms, because it will produce correct argument names for the form fields. If i would instead use a simple html <form> i would have to make sure to name all of my fields correctly.
IMO the parameter type should be changed from ?object to object|array|null
Unions are possible since PHP 8.0
Updated by Philipp Wrann 2 months ago
The bug has been introduced with this commit:
https://github.com/TYPO3/typo3/commit/528b90fea50622784dfdd2d651a6486e960b7460
IMO it is a bad practice to change things, that are not related to the current task, the method signature should have not been changed with the task described in the commit.
Please change the parameter type to the union described in the issue, otherwise i will need to create proxy ArrayObject classes foreach plugin where i used this very common pattern.