phpstan-laminas-framework
phpstan-laminas-framework copied to clipboard
Laminas Framework 3 extensions for PHPStan
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.[View this repository on the Mend.io Web Portal](https://developer.mend.io/github/Slamdunk/phpstan-laminas-framework). ## Awaiting Schedule The following updates are...
This PR contains the following updates: | Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | [phpunit/phpunit](https://phpunit.de/) ([source](https://redirect.github.com/sebastianbergmann/phpunit)) | `^9.6.21` -> `^11.4.0` | [](https://docs.renovatebot.com/merge-confidence/) |...
I don't know why but it's not loading some helpers. Is there something I should configure?  `.neon`  `service-manager.php` 
When I run rector with this extension rector fails. Running phpstan works fine. Ping @samsonasik ``` [ERROR] Could not process "module/EcommerceApi/tests/integration/ElasticsearchProductsCollectionQueryTest.php" file, due to: "System error: "Unable to resolve service...
I have few modules which do someting like this: ```php class Module { public function onBootstrap(MvcEvent $event): void { $config = $event->getApplication()->getServiceManager()->get('config'); // .... } } ``` This code hangs...
I would like to check in specific cases that response is `Laminas\ApiTools\ApiProblem\ApiProblemResponse`, but: ``` Instanceof between Laminas\Http\PhpEnvironment\Response and Laminas\ApiTools\ApiProblem\ApiProblemResponse will always evaluate to false. ```
As you know, a zend-mvc view has fields that `__get` can return, used like this: ``` $page = $this->getView()->page; ``` PHPStan says `Access to an undefined property` which makes sense....
See https://github.com/Slamdunk/phpstan-laminas-framework/issues/5#issuecomment-582316400
Right now this PHPStan extension is not compatible with Laminas ServiceManager v4 which was released on March 4 2024: https://github.com/laminas/laminas-servicemanager/releases/tag/4.0.0 There's probably more to it than the obvious issue described...