Skip to content

Port to TypegraphQL-Prisma #6

@oohwooh

Description

@oohwooh

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions