Hi,
i have found a bug in method Luracast\Restler\Scope::resolve($className, array $scope)
The method get a string, which should represent a PHP-class. I can't say why, but in fact, the method is called with string-values like 'integer', 'string' or 'array'...so restler 'think' it must resolve a PHP-class, but it currently also try to resolve primitive dataTypes.
The bug seems to not be critical. But in my case (we use restler in combination with the TYPO3-CMS) the bug is critical, because the bug results in a lot of (needless) 'TYPO3-Caching-Requests' (because TYPO3 cache infos about PHP-classes in a file-based cache), which resulted in pure performance and crashed some REST-API-calls.
Arul-
commented
7 years ago
Hi, i have found a bug in method Luracast\Restler\Scope::resolve($className, array $scope)
The method get a string, which should represent a PHP-class. I can't say why, but in fact, the method is called with string-values like 'integer', 'string' or 'array'...so restler 'think' it must resolve a PHP-class, but it currently also try to resolve primitive dataTypes.
The bug seems to not be critical. But in my case (we use restler in combination with the TYPO3-CMS) the bug is critical, because the bug results in a lot of (needless) 'TYPO3-Caching-Requests' (because TYPO3 cache infos about PHP-classes in a file-based cache), which resulted in pure performance and crashed some REST-API-calls.