Project

General

Profile

Actions

Bug #103162

closed

The f:form ViewHelper can not handle arrays as object attribute anymore

Added by Philipp Wrann 9 months ago. Updated about 1 month ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Fluid
Start date:
2024-02-20
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
12
PHP Version:
8.2
Tags:
Complexity:
Is Regression:
Sprint Focus:

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


Related issues 1 (0 open1 closed)

Has duplicate TYPO3 Core - Bug #105146: TYPO3\CMS\Fluid\ViewHelpers\Form\AbstractFormViewHelper::renderHiddenIdentityField(): Argument #1 ($object) must be of type ?object, array givenClosed2024-09-26

Actions
Actions

Also available in: Atom PDF