add minio service and start workaround on CI pipeline

src/Minio/minio.module.ts

@@ -0,0 +1,5 @@
+import { Module, Global } from '@nestjs/common';
+
+@Global()
+@Module({})
+export class MinioModule {}

src/Minio/minio.service.ts

@@ -0,0 +1,9 @@
+import { forwardRef, Inject, Injectable } from '@nestjs/common';
+
+@Injectable()
+export class MinioService {
+  constructor(
+    @Inject(forwardRef(() => ConfigService))
+    private configService: ConfigService,
+  ) {}
+}

src/UploadedDocument/uploadeddocument.schema.ts

@@ -28,7 +28,7 @@ export class UploadedDocumentSchema extends PothosSchema {
         status: t.exposeString('status'),
         type: t.exposeString('type'),
         documentUrl: t.exposeString('documentUrl'),
-        uploadedAt: t.expose('uploadedAt', { type: 'DateTime' as any }),
+        uploadedAt: t.expose('uploadedAt', { type: 'DateTime' }),
       }),
     });
   }
@@ -60,5 +60,24 @@ export class UploadedDocumentSchema extends PothosSchema {
         },
       }),
     }));
+
+    // Mutations section
+    this.builder.mutationFields((t) => ({
+      createUploadedDocument: t.prismaField({
+        type: this.uploadedDocument(),
+        args: {
+          input: t.arg({
+            type: this.builder.generator.getCreateInput('UploadedDocument'),
+            required: true,
+          }),
+        },
+        resolve: async (query, root, args, ctx, info) => {
+          return await this.prisma.uploadedDocument.create({
+            ...query,
+            data: args.input,
+          });
+        },
+      }),
+    }));
   }
 }