[!IMPORTANT]

Read my conclusion after using prisma-nestjs-graphql.

Filtering using prisma-nestjs-graphql

1. pnpm add @paljs/plugins
   pnpm add --save-dev prisma-nestjs-graphql
   nx add @nx-tools/nx-prisma
   nx g @nx-tools/nx-prisma:configuration --project botprobe-nest --database postgresql
   

   [!NOTE]

   • @paljs/plugin will hlp us to fetch exactly the data that we wanted. Though please note that it is not gonna solve the N+1 issue.
   • Change the project name to whatever is yours.

   • If your models have Decimal or JSON types, you need to install:

     pnpm add graphql-type-json prisma-graphql-type-decimal
     

     Or we can create custom graphql scalar types for these types (learn more).

2. generator nestgraphql {
     provider = "node node_modules/prisma-nestjs-graphql"
     output   = "../src/@generated"
   }
   

   • Do not forget to add the @generated entry to your .gitignore.
   • You can use emitSingle to have a single index file containing all the generated args, etc.
   • Add requireSingleFieldsInWhereUniqueInput in case your table has only one field.

3. cd apps/botprobe-nest
   nest g module alert
   nest g service alert
   nest g resolver alert
   nest g module alert-type
   nest g service alert-type
   nest g resolver alert-type
   

4. Check apps/botprobe-nest to see what goes inside those files.
5. And to see how you should write e2e tests read the apps/botprobe-nest-e2e.

6. Use /// to customize the generated code:

   • /// @HideField().

   • For class-validator you need to:

     1. pnpm add class-validator class-transformer
        

     2. // src/main.ts
        import { ValidationPipe } from '@nestjs/common';
        // ...
        app.useGlobalPipes(new ValidationPipe());
        // ...
        

     3. generator nestgraphql {
          fields_Validator_from = "class-validator"
          fields_Validator_input = true
        }
        // ...
        model User {
          // ...
          /// @Validator.MinLength(3)
          name String
          // ...
        }
        // ...
        

        Find more examples in apps/botprobe-nest.

![IMPORTANT]

# According to my experiences with this lib there are a couple of things which needs your consideration:

Downsides IMO

1. The naming of input types does not make sense.
2. Optional fields are not optional in the generated TS class.
3. In apps/botprobe-nest I used @paljs/plugin which simplifies selecting the fields that client asked for. But be aware of these issues:
   • Prisma still sends separates queries to the underlying database.
4. prisma-nestjs-graphql does not delete the previous @generated before generating the new one (purgeOutput).
5. There is not any way to deprecate a relation field.
6. Pagination and fetching data from external APIs and incorporating them in your API requires a lot of manual work (learn more here):

   query {
     post {
       # `user` data is stored in our FusionAuth e.g.
       user {
         id
         username
       }
       # `commentsConnection` is implemented according to the Cursor-based Connections Spec.
       commentsConnection(
         first: 5
         after: "encodedValueWithBase64Algorithm"
       ) {
         edges {
           cursor
           node {
             id
             content
           }
         }
         pageInfo {
           hasNextPage
         }
       }
     }
   }
   

Upsides IMO

1. I did a quick npm trends and it seems that this lib reign supreme in Prisma but the downsides are too many: