search

pullflow-ai / sample-redwood

The App Framework for Startups
https://redwoodjs.com
MIT License
0 stars 0 forks source link

[Bug]: Prisma Model Changes Not Reflected in GraphQL API #8

Open alissa-pullflow opened 1 day ago

alissa-pullflow commented 1 day ago

What's not working?

After updating the Prisma schema to add a new relation between User and Post, the changes are not reflected in the GraphQL API. Running prisma generate and yarn rw prisma migrate dev completes successfully, but queries for the new relation still return null values. This suggests that the GraphQL API is not updating properly with Prisma changes, and documentation about how Prisma and RedwoodJS synchronize schema updates with the API could resolve the issue.

How do we reproduce the bug?

No response

What's your environment? (If it applies)

No response

Are you interested in working on this?

pullflow-ai[bot] commented 1 day ago

I've added the label 'bug/needs-info' because the issue describes a problem with Prisma model changes not being reflected in the GraphQL API, but lacks sufficient information for reproduction. The label 'documentation' is also added because the issue suggests that better documentation on how Prisma and RedwoodJS synchronize schema updates with the API could resolve the issue.

pullflow-ai[bot] commented 1 day ago

Hello @alissa-pullflow, I'm pullflow-ai, here to help with your issue.

It sounds like the changes in your Prisma schema aren't being reflected in your GraphQL API. Here are a few things you might consider checking:

  1. Ensure Migrations are Applied: Double-check that yarn rw prisma migrate dev has been run successfully and that the migrations have been applied to your database.

  2. Check GraphQL Schema: Make sure that your GraphQL schema has been updated to include the new relation. You might need to manually update your SDL files if they don't automatically reflect Prisma changes.

  3. Restart the Development Server: Sometimes, simply restarting your RedwoodJS development server can help in syncing the latest changes.

  4. Prisma Client: Ensure that the Prisma Client is up-to-date by running prisma generate after making schema changes.

If these steps don't resolve the issue, could you provide more details about your environment or any error messages you might be seeing?

Feel free to reach out if you need further assistance!