0 bytes on multiple files when use nestjs inputType

When I load images with a resolver in GraphQL using a inputType class in NestJS, I get 0-byte files when i upload to s3. However, if I add everything as args, the files arrive correctly, I don’t see too many differences, what could be the problem?

mutation:

@Mutation(() => Course)
async addResources(
  @Args({ name: 'input', type: () => CreateResources }) input: CreateResources,
  @CurrentUser() user: User
) {
  const type = EXTRARESOURCES;
  const result = await this.courseService.addExtraResources(
    user,
    input,
    type
  );
  if (!result) errorInvalidInput(type);
  return result;
}

inputType

@InputType()
export class CreateResources {
  @IsOptional()
  @Field(() => [CreateResourceLinkInput], { nullable: true })
  links: CreateResourceLinkInput[];

  @IsOptional()
  @Field(() => [CreateResourceVideoInput], { nullable: true })
  videos: CreateResourceVideoInput[];

  @IsOptional()
  @Field(() => [GraphQLUpload], { nullable: true })
  documents: Promise<[FileUpload]>;

  @IsOptional()
  @Field(() => [GraphQLUpload], { nullable: true })
  images: Promise<[FileUpload]>;
}

All as args

@Mutation(() => Course)
async AddResources(
  @Args({ name: 'links', type: () => [CreateResourceLinkInput], nullable: true }) links: [CreateResourceLinkInput],
  @Args({ name: 'videos', type: () => [CreateResourceVideoInput], nullable: true }) videos: [CreateResourceVideoInput],
  @Args({ name: 'documents', type: () => [GraphQLUpload], nullable: true }) documents: [FileUpload],
  @Args({ name: 'images', type: () => [GraphQLUpload], nullable: true }) images: [FileUpload],
  @CurrentUser() user: User
) {
  const type =EXTRARESOURCES;
  const input = {
    links,
    videos,
    documents,
    images
  };
  const result = await this.courseService.addExtraResources(
    user,
    input,
    type
  );
  if (!result) errorInvalidInput(type);
  return result;
}

[SergioSuarezDev]

Hi guys.

After reading and reading and testing and testing. The problem comes from the “class-validator” module that is used in Nestjs because the validator internally tries to transform the object (since the file instance is an object) and fails. By adding the @Exclude decorator to the GraphQLUpload field, the files are received correctly.

Like this:

@InputType('CreateResources')
export class CreateResources {
  @Exclude()
  @IsOptional()
  @Field(() => [GraphQLUpload], { nullable: true })
  documents?: Promise<FileUpload>[];

  @Exclude()
  @IsOptional()
  @Field(() => [GraphQLUpload], { nullable: true })
  images?: Promise<FileUpload>[];

  @IsOptional()
  @IsNumber()
  @Field(() => Int, { nullable: true })
  order: number;
}

[jaydenseric]

Closing because this issue doesn’t appear to be actionable on the graphql-upload side, but feel free to keep the conversation going. I’m happy to answer any questions you may have about graphql-upload, but I can’t be of much help with NestJS stuff since I’ve never used it in a project before. Maybe you’ll figure it out, or someone here can offer more advice, but the NestJS community might be a better place to ask about these problems.