Issue Feature Closed

#72270Form name attribute with depth for complex use cases

Philipp Rönsch 12/16/15, 16:21 updated 01/25/17, 16:04

Description

I want to suggest this feature for tx_form to handle complex objects.
This requires a change to the handling of the name attribute of inputs.

The following should be possible:

FORM CONFIG:

prefix = tx_form
...
10 = TEXTLINE
10{
    name = object.property.subproperty
    label {
        value = Vorname
    }
}
...

HTML OUTPUT:

<input type="text" name="tx_form_form[tx_form][object][property][subproperty]" />

In the end this increases the versatility of tx_form, where complex forms could be handled by new/custom post processors.

The changes could could be made to:
- FormUtility->sanitizeNameAttribute(), where the . notation could be kept.
- HandleIncomingFormValues->handleIncomingFormValues, where the depth of the form values must be respected
- FormUtility/Element, could be extended to hold the full name, including prefix, for display accross all templates OR a ViewHelper for the name is added to all templates

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.