class-validators for "child" or sub-inputs not firing.

[kevin-mitchell]

Hello!

I have a ProductResolver, that has a ProductInput @InputType(). The ProductInput has a "child" input called PricingInput.

The class-validators on the "child" PricingInput don't appear to be called, only the ProductInput.

I'm wondering if I'm missing something wrong, if this is just an unsupported feature, etc. Here is a simplified example:

Resolver

Here is the resolver. Obviously this is just an example, not the full file / class..

// .../resolvers/product-resolver.ts

@Service()
@Resolver(Product)
export class ProductResolver {
  
...

  @Mutation(() => Product)  
  addProduct(
    @Arg('newProductInput')
    newProductInput: NewProductInput,    
  ): Promise<Product> {
    return this.productService.addNew({
      data: newProductInput,
    });
  }
}

Top level @InputType with working class-validator annotations

This is the "top level" @InputType, and note that these class-validators "work"... In this file you can see where / now I include the PricingInput (this is the one that doesn't fire).

// .../resolvers/product-input.ts

...

import { ProductInput } from './product-input-type';

@InputType()
export class NewProductInput {
  @Field({ nullable: true })
  structure?: string;

  // this validator as well as any other in this class fire with the annotations as expected
  @Field(() => GraphQLJSON)
  @ContentMatchesJSONSchema() // custom validator - this fires
  metadata?: object;

...
  
  // Here is where I'm including the "nested" "child" Input
  @Field(() => [PricingInput], { nullable: true })
  pricing?: PricingInput[];
}

"Child" @InputType without working class-validator annotations

And finally here is the "child" class / input type. Note that the fields show up and everything works in terms of the GraphQL Schema generation, it's just that the validator annotations don't appear to be triggered.

...

@InputType()
export class PricingInput {
  
  ...

  // this validator doesn't fire. Nor do out of the box class-validators
  @Field(() => GraphQLJSON)
  @ContentMatchesJSONSchema()
  pricingProperties?: object;

}

<3 thanks for any help!

[kevin-mitchell]

Turns out I should have probably read the documentation closer.

There is a section on validating nested objects, and as far as I can tell this is working as advertised.

In case anybody finds this and the exact syntax isn't clear to you, this is what worked for me. In my top level NewProductInput example above, I added @ValidateNested({ each: true }) - in my case { each: true } was required because I have an array of PricingInput's. After adding this decorator, my PricingInput validator(s) fired as expected.

// .../resolvers/product-input.ts

...

import { ProductInput } from './product-input-type';

@InputType()
export class NewProductInput {
  @Field({ nullable: true })
  structure?: string;

  // this validator as well as any other in this class fire with the annotations as expected
  @Field(() => GraphQLJSON)
  @ContentMatchesJSONSchema() // custom validator - this fires
  metadata?: object;

...
  
  // Here is where I'm including the "nested" "child" Input
  @Field(() => [PricingInput], { nullable: true })
  @ValidateNested({ each: true })
  pricing?: PricingInput[];
}