-
Notifications
You must be signed in to change notification settings - Fork 114
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
Discussion about Prisma 2 integration #1
Comments
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@MichalLytek can you update the |
It's done on the branch but not released - I will try to make release once a week when I have something new to share. It's still a preview to get some feedback, not a lib for production usage. |
This work looks awesome. Thank you so much for it. Looking over it I do have one concern in my usage. I would like to store some data only in the database and not expose it to he user, like the password hash. Looking at the current schema I am not seeing any options to omit certain types from the generated Type Graphql code, would it be possible to add this and generate it using |
https://github.com/MichalLytek/type-graphql/tree/prisma#feedback |
😅 Missed that part thanks! |
i created fork this repo and replace decorators to use with nestjs, maybe it need anybody 👨💼 |
I've just released |
It contains support for |
Type-graphql with Prisma will be a great combination! |
I want to add that support for OpenCRUD could help a lot of people to migrate from Prisma 1 to TypeGraphQL + Prisma Framework more faster and smoother. I'm not sure that the new Prisma API currently has equivalents for everything that OpenCRUD has, and could be mapped 1-to-1 by just renaming fields (like Also, it must be said that OpenCRUD spec is dead, the Prisma team has not updated it for more than a year. |
This comment has been minimized.
This comment has been minimized.
More feedback: I'm currently trying to use this in a NestJS project and I find the whole |
This comment has been minimized.
This comment has been minimized.
@John0x @FluorescentHallucinogen
I'm not defining the shape of the inputs or its names - this integrations is build on top of the Prisma Client DMMF, so it's basically 1:1 translating of its API.
|
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I've decided to move to a separate repo for the
Also, all the release info will be using GitHub release board. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
I've just released the I won't publish notifications here anymore, so if you want to keep informed, please enable watching this repository releases: |
Hi @MichalLytek, I was wondering how stable this package is because I had a bad experience with Nexus Framework. (They did a good job, but they stopped to support recently so) |
You can join this gitter channel. There is a prisma2 room. |
Hi @MichalLytek I am running into some issues using Prisma v2.20.1 and typegraphql-prisma v0.13.1, which I currently believe is related to: prisma/prisma#6329. Do you know where progress is at for supporting Prisma v2.21.2? I believe this version of Prisma will resolve some of the issues I am having currently. Thanks! |
I guess as mentioned in the docs, this can be run |
@DakotaLarson |
@MichalLytek close this? It's confusing, I almost thought typergaphql-prisma was not compatible with Prisma 2. |
I am thrilled to present the first preview of the upcoming TypeGraphQL & Prisma Framework integration 🎉
You can install it right now - it's distributed as a package
typegraphql-prisma
on NPM:https://www.npmjs.com/package/typegraphql-prisma
All the docs (in readme), examples and the source code of the integration are located on the
prisma
branch of this repo (in the future it will be moved into amaster
branch when I finish converting the project to a monorepo):https://github.com/MichalLytek/type-graphql/tree/prisma
Currently released version
0.x
is just a preview - it lacks some customization option, like picking/omitting fields of object types to expose in the schema, as well as picking CRUD methods and exposed args. However, the base functionality is working well, so I strongly encourage you to give it a try and play with it.Any feedback about the developers experience, bug reports or ideas about new features or enhancements are very welcome. However, during the preview I would ask to use the dedicated Gitter room if you have any questions:
https://gitter.im/type-graphql/prisma2
If you have a bug report, feel free to add comments only in this issue, not to create a new issues, as I don't want to pollute the repo for now 😉
And in the near feature - when Prisma SDK will be ready - the
typegraphql-prisma
integration will also allow to use a code-first approach to build aschema.prisma
and GraphQL schema at once, using classes with decorators as a single source of truth. Stay tuned! 💪The text was updated successfully, but these errors were encountered: