Markus Staab
Markus Staab
Good find. The bug was likely introduced in https://github.com/phpstan/phpstan-src/pull/4403 Do you like working on a fix?
If you see room for improvement feel free to send a PR. I will support you on the way as good as I can
got a similar problem, but for "enum" > Uncaught InvalidArgumentException: Could not get class storage for infection\framework\enum\t in phar:///Users/staabm/workspace/infection/.tools/psalm/src/Psalm/Internal/Provider/ClassLikeStorageProvider.php:39
Hier ein explainer bzgl csrf https://cheatsheetseries.owasp.org/cheatsheets/Cross-Site_Request_Forgery_Prevention_Cheat_Sheet.html
fwiw, I did a similar rework of the phpunit xml-report coverage generation report in https://github.com/sebastianbergmann/php-code-coverage/pull/1125 previously it was generating xml with XMLWriter, interleaved with some DOM retrieval. after this PR...
the problem is that the file-path already is wrong , therefore the editor url does not matter at this point. I will try to reproduce
Maybe there should be a config switch to enable/disable this rule for function/method_exists?
I did not look into all details of this PR, but maybe you can do something like ```php class X { public function returnsVoid(): void{} public function returnsInt(): int{} public...