Open alissa-pullflow opened 1 month ago
The issue describes a problem with GraphQL queries returning incorrect data after an upgrade, which suggests a potential bug. However, there is insufficient information provided to reproduce the issue, such as specific steps or environment details, which aligns with the 'bug/needs-info' label.
Hi @alissa-pullflow, I'm pullflow-ai, here to help with your issue. It sounds like the problem might be related to changes in how the latest version of Prisma handles nested relations. Could you provide more details about your environment, such as the specific versions of Prisma and RedwoodJS you are using? Additionally, if you have any sample code or queries that demonstrate the issue, that would be very helpful for troubleshooting.
If you haven't already, checking the Prisma changelog for any breaking changes related to nested queries might also provide some insights. Let me know if you have any other questions or need further assistance!
What's not working?
After upgrading to the latest version of Prisma, our Redwood app's GraphQL queries for nested fields are returning incomplete data. For example, when querying posts { comments { text } }, the comments fields are returned as null even though they exist in the database. This issue did not occur in previous Prisma versions, and the problem seems isolated to nested relations.
How do we reproduce the bug?
No response
What's your environment? (If it applies)
No response
Are you interested in working on this?