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
support for doctrine/orm 3+? #551
Comments
I'm running: phpstan-doctrine When I upgraded Am I missing something, or is orm3 only supported WITH dbal4? I opened another issue before finding this one. EDIT: bumping to dbal4 is throwing different errors now:
|
related to #529 |
perhaps this is also related: #308 (comment) |
Please post the code that leads to "Method App\Users\Repository\UsersRolesRepository::findAll() should return array<App\Entity\UsersRoles> And please open a separate issue for the internal error, and post the stack trace as the error message instructs you to. |
Sure. Again, no errors at all on orm [orm3/dbal3] findAll() should return array<App\Entity\UsersRoles> but returns mixed
[orm3/dbal3] Internal error
|
if there's something you'd like me to test @ondrejmirtes, or some other info I can provide to help, just let me know. I know it's a bit thorny to debug these more complex dependency issues remotely, since it can't be easily replicated on phpstan,org as always, I value all of your work! |
I just upgraded orm from
2.19.0
to 3.1.0`, and as a result all of my repositories are now showing phpstan errors that this package was formerly handling, such as:This method was triggering no such error before the
orm
upgrade.I've confirmed the issue also exists on the latest
orm
3.0.x
The text was updated successfully, but these errors were encountered: