Merge branch 'docs/graphql-v10-update' of https://github.com/nestjs/docs.nestjs.com into docs/graphql-v10-update

Author: kamilmysliwiec

LICENSE

@@ -1,6 +1,6 @@
 (The MIT License)
 
-Copyright (c) 2017-2021 Kamil Myśliwiec <http://kamilmysliwiec.com>
+Copyright (c) 2017-2022 Kamil Myśliwiec <http://kamilmysliwiec.com>
 
 Permission is hereby granted, free of charge, to any person obtaining
 a copy of this software and associated documentation files (the

content/discover/who-uses.json

@@ -254,6 +254,7 @@
     "https://forwardigital.co.uk",
     "https://rozetka.com.ua",
     "https://www.itrio.net",
+    "https://alexishr.com",
     "https://dyrector.io",
     "https://stijlbreuk.nl"
   ]

content/graphql/federation.md

@@ -145,6 +145,8 @@ import { UsersService } from './users.service'; // Not included in this example
 export class AppModule {}
 ```
 
+A working example is available [here](https://github.com/nestjs/nest/tree/master/sample/31-graphql-federation-code-first/users-application) in code first mode and [here](https://github.com/nestjs/nest/tree/master/sample/32-graphql-federation-schema-first/users-application) in schema first mode.
+
 #### Federated example: Posts
 
 Post service is supposed to serve aggregated posts through the `getPosts` query, but also extend our `User` type with the `user.posts` field.
@@ -337,6 +339,8 @@ import { PostsService } from './posts.service'; // Not included in example
 export class AppModule {}
 ```
 
+A working example is available [here](https://github.com/nestjs/nest/tree/master/sample/31-graphql-federation-code-first/posts-application) for the code first mode and [here](https://github.com/nestjs/nest/tree/master/sample/32-graphql-federation-schema-first/posts-application) for the schema first mode.
+
 #### Federated example: Gateway
 
 Start by installing the required dependency:
@@ -375,6 +379,8 @@ import { GraphQLModule } from '@nestjs/graphql';
 export class AppModule {}
 ```
 
+A working example is available [here](https://github.com/nestjs/nest/tree/master/sample/31-graphql-federation-code-first/gateway) for the code first mode and [here](https://github.com/nestjs/nest/tree/master/sample/32-graphql-federation-schema-first/gateway) for the schema first mode.
+
 #### Federation with Mercurius
 
 Start by installing the required dependencies:

content/interceptors.md

@@ -236,7 +236,7 @@ export class ErrorsInterceptor implements NestInterceptor {
     return next
       .handle()
       .pipe(
-        catchError(err => throwError(new BadGatewayException())),
+        catchError(err => throwError(() => new BadGatewayException())),
       );
   }
 }
@@ -251,7 +251,7 @@ export class ErrorsInterceptor {
     return next
       .handle()
       .pipe(
-        catchError(err => throwError(new BadGatewayException())),
+        catchError(err => throwError(() => new BadGatewayException())),
       );
   }
 }
@@ -311,9 +311,9 @@ export class TimeoutInterceptor implements NestInterceptor {
       timeout(5000),
       catchError(err => {
         if (err instanceof TimeoutError) {
-          return throwError(new RequestTimeoutException());
+          return throwError(() => new RequestTimeoutException());
         }
-        return throwError(err);
+        return throwError(() => err);
       }),
     );
   };
@@ -330,9 +330,9 @@ export class TimeoutInterceptor {
       timeout(5000),
       catchError(err => {
         if (err instanceof TimeoutError) {
-          return throwError(new RequestTimeoutException());
+          return throwError(() => new RequestTimeoutException());
         }
-        return throwError(err);
+        return throwError(() => err);
       }),
     );
   };

content/middlewares.md

@@ -143,7 +143,7 @@ The `MiddlewareConsumer` is a helper class. It provides several built-in methods
 import { Module, NestModule, MiddlewareConsumer } from '@nestjs/common';
 import { LoggerMiddleware } from './common/middleware/logger.middleware';
 import { CatsModule } from './cats/cats.module';
-import { CatsController } from './cats/cats.controller.ts';
+import { CatsController } from './cats/cats.controller';
 
 @Module({
   imports: [CatsModule],
@@ -159,7 +159,7 @@ export class AppModule implements NestModule {
 import { Module } from '@nestjs/common';
 import { LoggerMiddleware } from './common/middleware/logger.middleware';
 import { CatsModule } from './cats/cats.module';
-import { CatsController } from './cats/cats.controller.ts';
+import { CatsController } from './cats/cats.controller';
 
 @Module({
   imports: [CatsModule],

content/security/authentication.md

@@ -761,7 +761,7 @@ Ensure the app is running, and test the routes using `cURL`.
 ```bash
 $ # GET /profile
 $ curl http://localhost:3000/profile
-$ # result -> {"statusCode":401,"error":"Unauthorized"}
+$ # result -> {"statusCode":401,"message":"Unauthorized"}
 
 $ # POST /auth/login
 $ curl -X POST http://localhost:3000/auth/login -d '{"username": "john", "password": "changeme"}' -H "Content-Type: application/json"

content/security/helmet.md

@@ -1,6 +1,6 @@
 ### Helmet
 
-[Helmet](https://github.com/helmetjs/helmet) can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately. Generally, Helmet is just a collection of 14 smaller middleware functions that set security-related HTTP headers (read [more](https://github.com/helmetjs/helmet#how-it-works)).
+[Helmet](https://github.com/helmetjs/helmet) can help protect your app from some well-known web vulnerabilities by setting HTTP headers appropriately. Generally, Helmet is just a collection of smaller middleware functions that set security-related HTTP headers (read [more](https://github.com/helmetjs/helmet#how-it-works)).
 
 > info **Hint** Note that applying `helmet` as global or registering it must come before other calls to `app.use()` or setup functions that may call `app.use()`. This is due to the way the underlying platform (i.e., Express or Fastify) works, where the order that middleware/routes are defined matters. If you use middleware like `helmet` or `cors` after you define a route, then that middleware will not apply to that route, it will only apply to middleware defined after the route.
 

content/techniques/http-module.md

@@ -128,6 +128,6 @@ If you want to reuse an existing options provider instead of creating a private
 ```typescript
 HttpModule.registerAsync({
   imports: [ConfigModule],
-  useExisting: ConfigService,
+  useExisting: HttpConfigService,
 });
 ```

content/websockets/gateways.md

@@ -21,7 +21,7 @@ $ npm i --save @nestjs/websockets @nestjs/platform-socket.io
 
 #### Overview
 
-In general, each gateway is listening on the same port as the **HTTP server**, unless your app is not a web application, or you have changed the port manually. This default behavior can be modified by passing an argument to the `@WebSocketGateway(80)` decorator where `80` is a chosen port number. You can also set a [namespace](https://socket.io/docs/rooms-and-namespaces/) used by the gateway using the following construction:
+In general, each gateway is listening on the same port as the **HTTP server**, unless your app is not a web application, or you have changed the port manually. This default behavior can be modified by passing an argument to the `@WebSocketGateway(80)` decorator where `80` is a chosen port number. You can also set a [namespace](https://socket.io/docs/v4/namespaces/) used by the gateway using the following construction:
 
 ```typescript
 @WebSocketGateway(80, { namespace: 'events' })
@@ -99,7 +99,7 @@ handleEvent(client, data) {
 }
 ```
 
-In the example above, the `handleEvent()` function takes two arguments. The first one is a platform-specific [socket instance](https://socket.io/docs/server-api/#socket), while the second one is the data received from the client. This approach is not recommended though, because it requires mocking the `socket` instance in each unit test.
+In the example above, the `handleEvent()` function takes two arguments. The first one is a platform-specific [socket instance](https://socket.io/docs/v4/server-api/#socket), while the second one is the data received from the client. This approach is not recommended though, because it requires mocking the `socket` instance in each unit test.
 
 Once the `events` message is received, the handler sends an acknowledgment with the same data that was sent over the network. In addition, it's possible to emit messages using a library-specific approach, for example, by making use of `client.emit()` method. In order to access a connected socket instance, use `@ConnectedSocket()` decorator.
 

src/app/homepage/newsletter/services/newsletter.service.ts

@@ -1,6 +1,6 @@
 import { HttpClient } from '@angular/common/http';
 import { Injectable } from '@angular/core';
-import { empty } from 'rxjs';
+import { EMPTY } from 'rxjs';
 import { catchError } from 'rxjs/operators';
 
 @Injectable({ providedIn: 'root' })
@@ -12,7 +12,7 @@ export class NewsletterService {
       'https://z93f42xq2l.execute-api.us-east-2.amazonaws.com/Stage/newsletter?token=db1f899025b5a59a76b6b34b2a013893';
     return this.httpClient
       .post(newsletterUrl, { email })
-      .pipe(catchError(() => empty()))
+      .pipe(catchError(() => EMPTY ))
       .toPromise();
   }
 }