-
Notifications
You must be signed in to change notification settings - Fork 34
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
Prisma one-to-many relation: Error: Unknown type #10
Comments
Hello @stepanic. ✨ Thank you for the complements. The project has come a long way. Also, yes you are right. Something seems to be broken right now with the Pal.js code generation. I have been upgrading the dependencies for this repo at a fairly rapid pace as of late. I was trying to get the repo working with the latest versions for this particular technology stack. Pal.js and Prisma versions can sometimes have discrepancies and have been notoriously finicky about breaking changes to the Prisma DMMF as new features within Prisma have been integrated in newer versions. Sometimes it takes some effort to get Pal.js and Prisma to gel well again. I have had hiccups before where some things would break due to advancing Prisma to a newer version. It seems to have happened again. It happens! ⛩ 🎐 Thanks for the heads up! Let me regress the semantic version numbers until things are at least in working order again. I'll freeze the version numbers within the |
Related: paljs/prisma-tools#252
|
I've tried a lot of combinations for Angular with Node but this is the most awesome starter :)), nice job.
ISSUE
When I update
schema.prisma
by adding simple one-to-many relationAnd after
npm run prisma:migrate
it is possible to insert data with Prisma Studio but it is not possible to start Node.js backend withnpm run start:api
.Interface
ProductUpdateManyMutationInput
is not generated (file:resolversTypes.ts
).The text was updated successfully, but these errors were encountered: