feat(validation): make class-validator truly optional dependency

Author: MichalLytek

CHANGELOG.md

@@ -6,6 +6,8 @@
 - **Breaking Change**: `AuthChecker` type is now "function or class" - update to `AuthCheckerFn` if the function form is needed in the code
 - **Breaking Change**: update `graphql-js` peer dependency to `^16.6.0`
 - **Breaking Change**: `buildSchemaSync` is now also checking the generated schema for errors
+- **Breaking Change**: `validate` option of `buildSchema` is set to `false` by default - integration with `class-validator` has to be turned on explicitly
+- **Breaking Change**: `validate` option of `buildSchema` doesn't accept anymore a custom validation function - use `validateFn` option instead
 - support class-based auth checker, which allows for dependency injection
 - allow defining directives for interface types and theirs fields, with inheritance for object types fields (#744)
 - allow deprecating input fields and args (#794)

docs/installation.md

@@ -10,10 +10,10 @@ Before getting started with TypeGraphQL we need to install some additional depen
 
 ## Packages installation
 
-First, we have to install the main package, as well as [`graphql-js`](https://github.com/graphql/graphql-js) and [`class-validator`](https://github.com/typestack/class-validator) which are peer dependencies of TypeGraphQL:
+First, we have to install the main package, as well as [`graphql-js`](https://github.com/graphql/graphql-js) which is a peer dependency of TypeGraphQL:
 
 ```sh
-npm i graphql class-validator type-graphql
+npm i graphql type-graphql
 ```
 
 Also, the `reflect-metadata` shim is required to make the type reflection work:

docs/validation.md

@@ -16,7 +16,13 @@ We can also use other libraries or our own custom solution, as described in [cus
 
 ### How to use
 
-First we decorate the input/arguments class with the appropriate decorators from `class-validator`.
+First, we need to install the `class-validator` package:
+
+```sh
+npm i class-validator
+```
+
+Then we decorate the input/arguments class with the appropriate decorators from `class-validator`.
 So we take this:
 
 ```typescript
@@ -47,6 +53,15 @@ export class RecipeInput {
 }
 ```
 
+Then we need to enable the auto-validate feature (as it's disabled by default) by simply setting `validate: true` in `buildSchema` options, e.g.:
+
+```typescript
+const schema = await buildSchema({
+  resolvers: [RecipeResolver],
+  validate: true, // enable `class-validator` integration
+});
+```
+
 And that's it! 😉
 
 TypeGraphQL will automatically validate our inputs and arguments based on the definitions:
@@ -66,16 +81,8 @@ export class RecipeResolver {
 
 Of course, [there are many more decorators](https://github.com/typestack/class-validator#validation-decorators) we have access to, not just the simple `@Length` decorator used in the example above, so take a look at the `class-validator` documentation.
 
-This feature is enabled by default. However, we can disable it if we must:
-
-```typescript
-const schema = await buildSchema({
-  resolvers: [RecipeResolver],
-  validate: false, // disable automatic validation or pass the default config object
-});
-```
-
-And we can still enable it per resolver's argument if we need to:
+We don't have to enable this feature for all resolvers.
+It's also possible to keep `validate: false` in `buildSchema` options but still enable it per resolver's argument if we need to:
 
 ```typescript
 class RecipeResolver {
@@ -101,6 +108,7 @@ class RecipeResolver {
 ```
 
 Note that by default, the `skipMissingProperties` setting of the `class-validator` is set to `true` because GraphQL will independently check whether the params/fields exist or not.
+Same goes to `forbidUnknownValues` setting which is set to `false` because the GraphQL runtime checks for additional data, not described in schema.
 
 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!
 
@@ -193,15 +201,15 @@ It receives two parameters:
 - `argValue` which is the injected value of `@Arg()` or `@Args()`
 - `argType` which is a runtime type information (e.g. `String` or `RecipeInput`).
 
-The `validate` function can be async and should return nothing (`void`) when validation passes or throw an error when validation fails.
-So be aware of this while trying to wrap another library in `validate` function for TypeGraphQL.
+The `validateFn` option can be an async function and should return nothing (`void`) when validation passes or throw an error when validation fails.
+So be aware of this while trying to wrap another library in `validateFn` function for TypeGraphQL.
 
 Example using [decorators library for Joi validators (`joiful`)](https://github.com/joiful-ts/joiful):
 
 ```ts
 const schema = await buildSchema({
   // ...other options
-  validate: argValue => {
+  validateFn: argValue => {
     // call joiful validate
     const { error } = joiful.validate(argValue);
     if (error) {

examples/automatic-validation/index.ts

@@ -10,6 +10,8 @@ async function bootstrap() {
   const schema = await buildSchema({
     resolvers: [RecipeResolver],
     emitSchemaFile: path.resolve(__dirname, "schema.gql"),
+    // remember to turn on validation!
+    validate: true,
   });
 
   // Create GraphQL server

examples/custom-validation/index.ts

@@ -12,7 +12,7 @@ async function bootstrap() {
     resolvers: [RecipeResolver],
     emitSchemaFile: path.resolve(__dirname, "schema.gql"),
     // custom validate function
-    validate: (argValue, argType) => {
+    validateFn: (argValue, argType) => {
       // call joiful validate
       const { error } = joiful.validate(argValue);
       if (error) {

examples/mixin-classes/index.ts

@@ -11,6 +11,7 @@ async function bootstrap() {
     resolvers: [UserResolver],
     emitSchemaFile: path.resolve(__dirname, "schema.gql"),
     skipCheck: true,
+    validate: true,
   });
 
   // Create GraphQL server

package.json

@@ -21,8 +21,13 @@
     "postgenerate:sponsorkit": "npx shx cp ./img/github-sponsors.svg ./website/static/img/github-sponsors.svg"
   },
   "peerDependencies": {
-    "class-validator": ">=0.14.0",
-    "graphql": "^16.6.0"
+    "graphql": "^16.6.0",
+    "class-validator": ">=0.14.0"
+  },
+  "peerDependenciesMeta": {
+    "class-validator": {
+      "optional": true
+    }
   },
   "dependencies": {
     "@types/node": "*",

src/errors/ArgumentValidationError.ts

@@ -1,3 +1,4 @@
+// @ts-ignore `class-validator` might not be installed by user
 import type { ValidationError } from "class-validator";
 
 export class ArgumentValidationError extends Error {

src/resolvers/create.ts

@@ -18,6 +18,7 @@ export function createHandlerResolver(
 ): GraphQLFieldResolver<any, any, any> {
   const {
     validate: globalValidate,
+    validateFn,
     authChecker,
     authMode,
     pubSub,
@@ -40,6 +41,7 @@ export function createHandlerResolver(
             resolverMetadata.params!,
             resolverData,
             globalValidate,
+            validateFn,
             pubSub,
           );
           if (isPromiseLike(params)) {
@@ -57,6 +59,7 @@ export function createHandlerResolver(
         resolverMetadata.params!,
         resolverData,
         globalValidate,
+        validateFn,
         pubSub,
       );
       const targetInstance = targetInstanceOrPromise;
@@ -81,6 +84,7 @@ export function createAdvancedFieldResolver(
   const targetType = fieldResolverMetadata.getObjectType!();
   const {
     validate: globalValidate,
+    validateFn: validateFn,
     authChecker,
     authMode,
     pubSub,
@@ -104,6 +108,7 @@ export function createAdvancedFieldResolver(
         fieldResolverMetadata.params!,
         resolverData,
         globalValidate,
+        validateFn,
         pubSub,
       );
       if (isPromiseLike(params)) {

src/resolvers/helpers.ts

@@ -10,11 +10,13 @@ import { AuthMiddleware } from "../helpers/auth-middleware";
 import { convertArgsToInstance, convertArgToInstance } from "./convert-args";
 import isPromiseLike from "../utils/isPromiseLike";
 import { ValidateSettings } from "../schema/build-context";
+import { ValidatorFn } from "../interfaces/ValidatorFn";
 
 export function getParams(
   params: ParamMetadata[],
   resolverData: ResolverData<any>,
   globalValidate: ValidateSettings,
+  validateFn: ValidatorFn<object> | undefined,
   pubSub: PubSubEngine,
 ): Promise<any[]> | any[] {
   const paramValues = params
@@ -27,13 +29,15 @@ export function getParams(
             paramInfo.getType(),
             globalValidate,
             paramInfo.validate,
+            validateFn,
           );
         case "arg":
           return validateArg(
             convertArgToInstance(paramInfo, resolverData.args),
             paramInfo.getType(),
             globalValidate,
             paramInfo.validate,
+            validateFn,
           );
         case "context":
           if (paramInfo.propertyName) {