-
-
Notifications
You must be signed in to change notification settings - Fork 78
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
Call to method Drupal\Core\Entity\Query\QueryInterface::accessCheck() with false will always evaluate to true. #508
Comments
This is an unexpected side effect from the type-specifying extension added in #497. Can you paste a sample of the code? I feel the test suite didn't fail due to tests not running with only a specific set of rules. I am assuming it is chained methods causing this error. |
Sure @mglaman sorry I should've included some examples
Even if I split the
and
both error. |
Here's a trimmed down paste of our phpstan config too if that changes anything
|
Thanks to @dpi for pointing out the errors go away when strict is disabled by removing the |
I'm also seeing errors on every access check upon updating with the following config:
|
Odd that it would pass when the phpstan-strict-rules is removed from configuration. The rule violation appears to come from
It looks like it is due to phpstan-strict-rules enables this flag, which is why it seemed to stop showing up. It enforces this flag regardless your analysis level
|
1.1.29 resolves this for me, thanks |
thanks for verifying! |
We just updated to 1.1.28 and every single
accessCheck(FALSE)
call is throwing this error.The text was updated successfully, but these errors were encountered: