MichalLytek / MichalLytek/typegraphql-prisma

Code-first approach using classes with decorators as a single source of truth

Open
#9 3 comments 0 reactions 0 assignees View on GitHub
priority:low question
Dominant language
TypeScript
Stars
918
Forks
130
PR merge metrics
No merged PRs in 30d

Description

From https://github.com/MichalLytek/typegraphql-prisma/issues/1#issue-714873665:
> 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 a `schema.prisma` and GraphQL schema at once, using classes with decorators as a single source of truth. Stay tuned! 💪

Are we there yet? Is the Prisma SDK ready? If not, what exactly is missing?

Recently I've been chatting with @divyenduz and he asked to open issue(s) about this in Prisma repo(s), so the Prisma team would have them in mind.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the Prisma SDK status and the existing code-first discussion linked in the issue. Identify what would be required for classes with decorators to generate both schema.prisma and the GraphQL schema, and record which SDK capabilities are still missing. Done means the status and scope are clearly documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
graphql, typescript
Domain
backend-api-design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.