-
Notifications
You must be signed in to change notification settings - Fork 93
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AbstractViewHelper::isValidType misses more simple types like int, float #1021
Comments
If we would add scalar types here, a lot of templates would break. I don't think that it's a good idea to throw an exception if the user inputs Can you elaborate what the exact problem is and what you'd like to achieve? |
The problem is that fluid looks for classes which are simple types which it shouldn't do. |
So it's just an implementation problem, not user-facing? |
yes, internally only |
if i understood correctly, the background of this issue was this reported issue/patch: https://review.typo3.org/c/Packages/TYPO3.CMS/+/87424 |
yes, this is where i originally started from and realized the reported issue here. |
That's what I had in mind as well, but that's why I asked: The issue is that some input values are not cast correctly. For example, if I'd suggest to close this issue and to write a more general issue instead that describes the problem of the Core issue. |
Nevermind, sorry. :) I'd suggest creating a separate issue for the casting behavior. This one is fine, though I would not consider it high priority in contrast to the type casting. |
When I define an argument as int, it actually tries to load a class named "int" which of course doesn't exist here:
https://github.com/TYPO3/Fluid/blob/main/src/Core/ViewHelper/AbstractViewHelper.php#L361
Instead all simple types should be checked manually without checking if
class_exists
.The text was updated successfully, but these errors were encountered: