PropertyMapper directly throws TargetNotFoundException
Since TYPO3 6.2.15 the
PropertyMapper directly throws a
TYPO3\CMS\Extbase\Property\Exception\TargetNotFoundException if thrown by a type converter instead of encapsulating it once with a general
TYPO3\CMS\Extbase\Property\Exception just like before.
This is a change in behavior and affects all code which relied on the previous structure to trigger e.g. the regular pageNotFoundHandling of TYPO3.
#2 Updated by Mathias Brodala over 3 years ago
- Status changed from New to Closed
- Assignee deleted (
- Is Regression changed from Yes to No
This issue actually is none. The API of
PropertyMapper::convert() states that it may throw exceptions of type
TYPO3\CMS\Extbase\Property\Exception\TargetNotFoundException derives from that exception type, any
catch statement for the former will also cover the latter. Thus no API breakage after all.