-
-
Notifications
You must be signed in to change notification settings - Fork 475
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
Update PHPStan to 2.x #1492
Update PHPStan to 2.x #1492
Conversation
composer.lockPackage changes
Dev Package changes
Settings · Docs · Powered by Private Packagist |
@staabm if I can bug you here.. I left 3 errors out of the baseline because I think they might be bugs in phpstan-dba. At least the last two errors. The first one I think might be a phpstan-doctrine issue rather.
I'm not sure if there is a way to express that the DB contains only lists and not arrays.. This would have to be on a "trust me it's true" basis of course. Probably a feature request for phpstan-doctrine?
I think that could be fixed in phpstan-dba.. a
Not sure what's going on there.. the code is quite simple so I don't understand why it falls back to array here. Is |
I guess its a phpstan-doctrine thing.. it doesn't look like related to DBA but more like ORM?
that should already be supported, in case you enable
the query builder is not supported in phpstan-dba until now. we don't know yet how the query looks like the builder is returning |
maybe thats something phpstan-doctrine can provide, as they already do the query-builder introspection for typing |
I would say that adding this error in the |
I think phpstan-doctrine indeed does not support refining types for array results, only for object hydration. |
The composer.lock diff comment has been updated to reflect new changes in this PR. |
Ok thanks both. I put two more in the baseline and fixed array columns to be json now so that got rid of the list issue. |
No description provided.