Add check on literal in TypeHandlingUtility::isCollectionType
Add a check to 'isLiteral' before doing expensive 'class_exists' operations trying to resolve objects for literals like: string, int, etc.
Maybe the ValidatorResolver could also do a check on a 'literal' before doing a 'class_exists' in 'buildBaseValidatorConjunction'.
Updated by Arjen Hoekema almost 7 years ago
The 'class_exists' performance problem is likely only an issue when you're not running in 'Production' context (especially in TYPO3 6.2/Extbase). The class loading cache information is not cached in 'Development' context. But several other autoloaders (from Composer packages) could be triggered to resolve classes for literal/primitive types.