-
-
Notifications
You must be signed in to change notification settings - Fork 74
Make types compatible with ORM/ODM drivers #374
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
Conversation
|
Here is the output of Psalm on ORM with this: |
|
Why not implementing the generic type instead of |
|
@stof I plan on doing it, but on 3.4.x since it is no bugfix (which this is from an SA point of view; the types are plain wrong here). |
|
Well, as the types are plain wrong, I would consider that the fix might be to put directly the right type as a replacement (which btw might generate less new SA errors in the ORM than your patch) |
|
Ok, let me give it a try. |
It does not look like the implementations for these methods return ClassMetadata objects.
|
@stof I gave it a try, and I need more changes on ORM to obtain the exact same output as above. On top of that, there are quite a few hurdles to overcome to get it to work on persistence itself, so I think this should be contributed on 3.4.x. Here is a preview of the issues: |
|
I think the fact that TestFileDriver actually returns ClassMetadata objects (for which SA tools infer |
|
@stof that and using |
It does not look like the implementations for these methods every return ClassMetadata objects.