-
-
Notifications
You must be signed in to change notification settings - Fork 78
RenderCallbackRule
ignores ::trustedCallbacks()
#561
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
Comments
Yep, this is a big gap. I thought I had documented it in the code with a |
|
Problem: we would need to call the method to get its values. I think. Even though the method is static, I don't believe it's return values can be parsed that way. |
Ideas:
We can then do So:
$foo should have the method names, then. |
The PR is almost ready, but it crashes on Drupal core due to the way a class fixture is defined. |
Bug report
(Now that all Entity Query problems seem to be solved, I looked a bit closer at the Trusted Callbacks, so expect some more issues on that)
Currently
\mglaman\PHPStanDrupal\Rules\Drupal\RenderCallbackRule
only checks if the class implementsTrustedCallbackInterface
.However the callbacks should also be in the return array from
trustedCallbacks()
to be trusted.Now I highly doubt that people "in the wild" go through the trouble of creating callbacks and making sure the containing class implements
TrustedCallbackInterface
and finally don't add the callback totrustedCallbacks()
, so the impact seems low.However what we're currently doing seems incorrect.
Code snippet that reproduces the problem
See testcases in (extended)
tests/src/Rules/data/bug-543.php
The text was updated successfully, but these errors were encountered: