You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are looking to move entities out of the Wasp file and into a dedicated Prisma file. Benefits of doing this are: tooling support, better Prisma feature support (enums, generators, datasources etc.), less maintenance in the Wasp compiler (maybe).
There are many open questions:
how does the Wasp compiler get info about entities then?
what is supported by Wasp in the Prisma file?
where and how do we handle migrations?
how do users run Prisma commands?
That's why we'll start first with an RFC and then from that we expect to create a detailed action plan on how to achieve this.
The text was updated successfully, but these errors were encountered:
We are looking to move entities out of the Wasp file and into a dedicated Prisma file. Benefits of doing this are: tooling support, better Prisma feature support (enums, generators, datasources etc.), less maintenance in the Wasp compiler (maybe).
There are many open questions:
That's why we'll start first with an RFC and then from that we expect to create a detailed action plan on how to achieve this.
The text was updated successfully, but these errors were encountered: