Bug #79412
closedEpic #77909: Enhance EXT:form
Feature #77910: Introduce new form framework
Ext:form - Finisher dies on parseOption if a formvalue should be used which is not a string
100%
Description
You can encapsulate a finisher option value with {}.
This enables you to access every getable property from the TYPO3\CMS\Form\Domain\Runtime.
For example you can set the "subject" option value from the EmailToSender finisher to something like {textfield-1}.
If you do so, the subject option value will be filled with the submitted data from the formelement with the identifier 'textfield-1'.
This is done by the function TYPO3\CMS\Form\Domain\Finishers\AbstractFinisher::parseOption().
parseOption fails if such a referenced formelement value contains non text value like a DateTime object.
This happens if a formelement do some property mapping stuff.
With this patchset, parseOption replace finisher option values with formelement values only if the formelement value is a string.
In addition, this enables you to replace non text values with your custom finisher implementations.
Updated by Gerrit Code Review almost 8 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51381
Updated by Gerrit Code Review almost 8 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51381
Updated by Gerrit Code Review almost 8 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/51381
Updated by Ralf Zimmermann almost 8 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 5b14551100c4a67ba15538981d0426bec1749463.