endykaufman / typegraphql-prisma-nestjs Goto Github PK

@EndyKaufman
Thank you for your help.

Eventually I was able to inject the primsa client to the context using this method:

GraphQLModule.forRootAsync({
      useFactory: async (configService: ConfigService) => ({
        autoSchemaFile:
          configService.get('GRAPHQL_SCHEMA_DEST') || './src/schema.graphql',
        debug: configService.get('GRAPHQL_DEBUG') === '1' ? true : false,
        playground:
          configService.get('PLAYGROUND_ENABLE') === '1' ? true : false,
        context: ({ req, prisma }) => ({ req, prisma: new PrismaClient() })
      }),

NestJS decided to reimplement all the features from scratch in type-graphql but using the same API meaning that every type-graphql import needs to be changed to @nestjs/graphql and the unimplemented decorators like FieldResolver and Arg need to be removed from the imports

Source: https://docs.nestjs.com/migration-guide#graphql

GraphQL#
In the version 6 major release of NestJS, we introduced the code-first approach as a compatibility layer between the type-graphql package and the @nestjs/graphql module. Eventually, our team decided to reimplement all the features from scratch due to a lack of flexibility. To avoid numerous breaking changes, the public API is backward-compatible and may resemble type-graphql.

In order to migrate your existing application, simply rename all the type-graphql imports to the @nestjs/graphql.

Hello!

Greenkeeper is no longer available for new installations.

The service will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020. Find out more at greenkeeper.io.

If this is your only Greenkeeper installation, you can just sign up for Snyk directly, it’s free for Open Source and even has free features for private projects as well.

Nevertheless, thanks for your interest in Greenkeeper! We’re sure your repositories will find a good home at Snyk ☀️🏡💜

All the best from everyone at Greenkeeper! 👋🤖🌴

Are there specific areas of this fork that differ with MichalLytek/type-graphql? Are there any plans to include the differences in the documentation?

What level of support will this fork have? Can I rely on it being relatively up to date with MichalLytek/type-graphql, or is this just an experiment that may be abandoned in the near future?

Its seems there is an issue with the generated crud opterations.

I have cloned your example project and tried adding the Recipes and Ingeredients to the prisma schema and removing the coded ./src/recipes/recipes.module.ts from the AppModule.

//  ./prisma/schema.prisma
model Recipes {
  id          Int       @default(autoincrement())
  title  String    @unique
  description String?   
  creationDate DateTime  @default(now()) @map("date_created")
  ingredients Ingredient[]
  @@map("recipies")
}

model Ingredient {
  id Int @unique @default(autoincrement())
  name String
  @@map("ingredient")
}

When I did this and attemted to regenerat the dal folder I ran into the following issue

src/dal/resolvers/crud/Recipes/RecipesCrudResolver.ts:19:9 - error TS2393: Duplicate function implementation.

19   async recipes(@Context() ctx: any, @Args() args: FindOneRecipesArgs): Promise<Recipes | null> {
           ~~~~~~~
src/dal/resolvers/crud/Recipes/RecipesCrudResolver.ts:27:9 - error TS2393: Duplicate function implementation.

27   async recipes(@Context() ctx: any, @Args() args: FindManyRecipesArgs): Promise<Recipes[]> {
           ~~~~~~~

Found 2 error(s).

error Command failed with exit code 1.

I looked into the generated crud operations and I found it had used the same name for the get one and get many functions

//  ./src/dal/resolvers/crud/Recipes/RecipesCrudResolver.ts
  @Query(_returns => Recipes, {
    nullable: true,
    description: undefined
  })
  async recipes(@Context() ctx: any, @Args() args: FindOneRecipesArgs): Promise<Recipes | null> {
    return ctx.prisma.recipes.findOne(args);
  }

  @Query(_returns => [Recipes], {
    nullable: false,
    description: undefined
  })
  async recipes(@Context() ctx: any, @Args() args: FindManyRecipesArgs): Promise<Recipes[]> {
    return ctx.prisma.recipes.findMany(args);
  }

After renaming my table in the schema.prisma file to Recipe the generated code worked fine.