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
As of #3874, we allow users to have prisma/schema.prisma instead of the default db/schema.prisma.
What happens now is that our codegen generates resolvers with import db from "db", instead of checking package.json to see where the prisma folder is
Suggestion
Read pacakge.json to check where the schema.prisma is and assume that importing from that folder should be the index.ts with default export of PrismaClient
What is the problem?
As of #3874, we allow users to have
prisma/schema.prisma
instead of the defaultdb/schema.prisma
.What happens now is that our codegen generates resolvers with
import db from "db"
, instead of checking package.json to see where the prisma folder isSuggestion
Read pacakge.json to check where the
schema.prisma
is and assume that importing from that folder should be theindex.ts
with default export of PrismaClientWhat are detailed steps to reproduce this?
db
toprisma
prisma/schema.prisma
fromdb/schema.prisma
All resolvers should import from "db" instead of "prisma"
Run
blitz -v
and paste the output here:From whenever #3874 is merged
Please include below any other applicable logs and screenshots that show your problem:
No response
The text was updated successfully, but these errors were encountered: