Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Port to TypegraphQL-Prisma #6

Open
oohwooh opened this issue Aug 23, 2022 · 0 comments
Open

Port to TypegraphQL-Prisma #6

oohwooh opened this issue Aug 23, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@oohwooh
Copy link
Member

oohwooh commented Aug 23, 2022 •
edited
Loading

This would be a reasonably large undertaking, and is not a priority by any means, but it would be a worthwhile endeavor imo.

We would need to add CustomResolvers for all the current resolvers to not break backwards-compatibility.

The main benefits from doing this:

  • Ease of future development (both to showcase-gql and any service that makes use of it)
  • Consistency with other services
  • Small enough to be a good first leap into porting the rest of our gql services to typegraphql-prisma
@oohwooh oohwooh added the enhancement New feature or request label Aug 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@oohwooh