Replies: 2 comments 8 replies
-
|
Try to play with explicit mixed ( |
Beta Was this translation helpful? Give feedback.
2 replies
-
|
Sorry, one more: https://phpstan.org/r/20dbafcb-e98c-48f8-adc6-e32a2bc15acd should unsafe offset access on normal arrays be reported too? Or is this on purpose? All of those would lead to warnings and null values. |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Is it on purpose that superglobal offset access is not handled strictly? I assume the reason is that implicit
mixedis created here or smth like that?E.g. https://phpstan.org/r/924c008a-eb32-4442-98a3-14545bbd8f83
I was expecting that PHPStan also strictly checks the
$_POSToffset and then later the usage of the$argsarray. Any suggestions in how to work with that? I try to explain to colleagues that we should handle this type-safe but we seem to be doing this kind of in the dark since PHPStan is not checking it.Or am I missing something obvious (config?) here?
Beta Was this translation helpful? Give feedback.
All reactions