-
Notifications
You must be signed in to change notification settings - Fork 102
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
Query result type inference often not working with getOneOrNullResult #271
Comments
/cc @arnaud-lb |
Hi @janedbal Currently, Query result type inference supports only
One way to get type inference out of (See #232 (comment) for details on how each getResult() variant is supported.) |
I see, thanks for response, I'll force passing hydration type to getOneOrNullResult in our codebase to make it analysable. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
See failures in #270, all the new getOneOrNullResult are infered as mixed even though the getResult works fine.
E.g. here
The text was updated successfully, but these errors were encountered: