docs(inputs): add info about validating nested inputs

MichalLytek · Nov 10, 2019 · 032b97b · 032b97b
1 parent 32f82e3
commit 032b97b
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 0 deletions.
diff --git a/CHANGELOG.md b/CHANGELOG.md
@@ -11,6 +11,7 @@
 - add basic support for directives with `@Directive()` decorator (#369)
 ### Fixes
 - refactor union types function syntax handling to prevent possible errors with circular refs
+- fix transforming and validating nested inputs and arrays (#462)
 
 ## v0.17.5
 ### Features

diff --git a/docs/validation.md b/docs/validation.md
@@ -98,6 +98,8 @@ Note that by default, the `skipMissingProperties` setting of the `class-validato
 
 GraphQL will also check whether the fields have correct types (String, Int, Float, Boolean, etc.) so we don't have to use the `@IsOptional`, `@Allow`, `@IsString` or the `@IsInt` decorators at all!
 
+However, when using nested input or arrays, we always have to use [`@ValidateNested()` decorator](https://github.com/typestack/class-validator#validating-nested-objects) or [`{ each: true }` option](https://github.com/typestack/class-validator#validating-arrays) to make nested validation work properly.
+
 ## Response to the Client
 
 When a client sends incorrect data to the server: