You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, contributor from Joomla again. I've been chasing an issue for way to long the last few days where phpstan reported a method to be missing, even though it is in our composer dependencies. We have a wrapper for filesystem operations and that wrapper is a standalone package which we add via composer. For system updates via browser however we have a bootstrap file which contains parts of that wrapper. That allows us to upgrade the dependency and still have a b/c version of that available. It also simplifies booting our app.
The problem now is, that the dependency is in our vendor directory and is properly parsed. Afterwards however it is parsing the bootstrap file in our normal codebase and seems to overwrite the information from the vendor folder. Since in our case the bootstrap file only contains slimmed down versions of the wrapper classes, phpstan now reports unknown static methods.
It would be good if phpstan would report when it finds the same class multiple times to protect against that.
Did PHPStan help you today? Did it make you happy in any way?
No response
The text was updated successfully, but these errors were encountered:
Feature request
Hello, contributor from Joomla again. I've been chasing an issue for way to long the last few days where phpstan reported a method to be missing, even though it is in our composer dependencies. We have a wrapper for filesystem operations and that wrapper is a standalone package which we add via composer. For system updates via browser however we have a bootstrap file which contains parts of that wrapper. That allows us to upgrade the dependency and still have a b/c version of that available. It also simplifies booting our app.
The problem now is, that the dependency is in our vendor directory and is properly parsed. Afterwards however it is parsing the bootstrap file in our normal codebase and seems to overwrite the information from the vendor folder. Since in our case the bootstrap file only contains slimmed down versions of the wrapper classes, phpstan now reports unknown static methods.
It would be good if phpstan would report when it finds the same class multiple times to protect against that.
Did PHPStan help you today? Did it make you happy in any way?
No response
The text was updated successfully, but these errors were encountered: