Merge branch 'master' into feature/dark-mode

Author: Tony133

content/openapi/introduction.md

@@ -146,6 +146,7 @@ export interface ExpressSwaggerCustomOptions {
   validatorUrl?: string;
   url?: string;
   urls?: Record<'url' | 'name', string>[];
+  patchDocumentOnRequest?: <TRequest = any, TResponse = any> (req: TRequest, res: TResponse, document: OpenAPIObject) => OpenAPIObject;
 }
 ```
 

content/recipes/swc.md

@@ -135,14 +135,14 @@ declare a `generate-metadata.ts` file near the `main.ts` file with the following
 
 ```ts
 import { PluginMetadataGenerator } from '@nestjs/cli/lib/compiler/plugins';
-import { ReadonlyVisitor } from '@nestjs/swagger';
+import { ReadonlyVisitor } from '@nestjs/swagger/dist/plugin';
 
 const generator = new PluginMetadataGenerator();
 generator.generate({
   visitors: [new ReadonlyVisitor({ introspectComments: true, pathToSource: __dirname })],
   outputDir: __dirname,
   watch: true,
-  tsconfigPath: 'tsconfig.build.json',
+  tsconfigPath: 'apps/<name>/tsconfig.app.json',
 });
 ```
 

content/security/rate-limiting.md

@@ -116,7 +116,7 @@ export class WsThrottlerGuard extends ThrottlerGuard {
   }
 }
 ```
-> info **Hint** If you using ws, it is necessary to replace the `_socket` with `conn`
+> info **Hint** If you are using ws, it is necessary to replace the `_socket` with `conn`
 
 There's a few things to keep in mind when working with WebSockets:
 

content/techniques/cookies.md

@@ -14,7 +14,7 @@ $ npm i -D @types/cookie-parser
 Once the installation is complete, apply the `cookie-parser` middleware as global middleware (for example, in your `main.ts` file).
 
 ```typescript
-import cookieParser from 'cookie-parser';
+import * as cookieParser from 'cookie-parser';
 // somewhere in your initialization file
 app.use(cookieParser());
 ```
@@ -49,7 +49,7 @@ findAll(@Res({ passthrough: true }) response: Response) {
 }
 ```
 
-> warning **Warning** If you want to leave the response handling logic to the framework, remember to set the `passthrough` option to `true`, as shown above. Read more [here](/controllers#appendix-library-specific-approach).
+> warning **Warning** If you want to leave the response handling logic to the framework, remember to set the `passthrough` option to `true`, as shown above. Read more [here](/controllers#library-specific-approach).
 
 > info **Hint** The `@Res()` decorator is imported from the `@nestjs/common`, while `Response` from the `express` package.
 
@@ -98,7 +98,7 @@ findAll(@Res({ passthrough: true }) response: FastifyReply) {
 
 To read more about `FastifyReply#setCookie()` method, check out this [page](https://github.com/fastify/fastify-cookie#sending).
 
-> warning **Warning** If you want to leave the response handling logic to the framework, remember to set the `passthrough` option to `true`, as shown above. Read more [here](/controllers#appendix-library-specific-approach).
+> warning **Warning** If you want to leave the response handling logic to the framework, remember to set the `passthrough` option to `true`, as shown above. Read more [here](/controllers#library-specific-approach).
 
 > info **Hint** The `@Res()` decorator is imported from the `@nestjs/common`, while `FastifyReply` from the `fastify` package.
 

content/techniques/file-upload.md

@@ -236,6 +236,18 @@ uploadFile(files) {
 }
 ```
 
+#### No files
+
+To accept `multipart/form-data` but not allow any files to be uploaded, use the `NoFilesInterceptor`. This sets multipart data as attributes on the request body. Any files sent with the request will throw a `BadRequestException`.
+
+```typescript
+@Post('upload')
+@UseInterceptors(NoFilesInterceptor())
+handleMultiPartData(@Body() body) {
+  console.log(body)
+}
+```
+
 #### Default options
 
 You can specify multer options in the file interceptors as described above. To set default options, you can call the static `register()` method when you import the `MulterModule`, passing in supported options. You can use all options listed [here](https://github.com/expressjs/multer#multeropts).

content/techniques/sql.md

@@ -992,10 +992,10 @@ There are three types of relations:
   </tr>
 </table>
 
-To define relations in entities, use the corresponding **decorators**. For example, to define that each `User` can have multiple photos, use the `@HasMany()` decorator.
+To define relations in models, use the corresponding **decorators**. For example, to define that each `User` can have multiple photos, use the `@HasMany()` decorator.
 
 ```typescript
-@@filename(user.entity)
+@@filename(user.model)
 import { Column, Model, Table, HasMany } from 'sequelize-typescript';
 import { Photo } from '../photos/photo.model';
 

content/techniques/task-scheduling.md

@@ -258,7 +258,7 @@ The `getCronJob()` method returns the named cron job. The returned `CronJob` obj
 
 > info **Hint** Use `toDate()` on `moment` objects to render them in human readable form.
 
-**Create** a new cron job dynamically using the `SchedulerRegistry.addCronJob()` method, as follows:
+**Create** a new cron job dynamically using the `SchedulerRegistry#addCronJob` method, as follows:
 
 ```typescript
 addCronJob(name: string, seconds: string) {
@@ -275,11 +275,11 @@ addCronJob(name: string, seconds: string) {
 }
 ```
 
-In this code, we use the `CronJob` object from the `cron` package to create the cron job. The `CronJob` constructor takes a cron pattern (just like the `@Cron()` <a href="techniques/task-scheduling#declarative-cron-jobs">decorator</a>) as its first argument, and a callback to be executed when the cron timer fires as its second argument. The `SchedulerRegistry.addCronJob()` method takes two arguments: a name for the `CronJob`, and the `CronJob` object itself.
+In this code, we use the `CronJob` object from the `cron` package to create the cron job. The `CronJob` constructor takes a cron pattern (just like the `@Cron()` <a href="techniques/task-scheduling#declarative-cron-jobs">decorator</a>) as its first argument, and a callback to be executed when the cron timer fires as its second argument. The `SchedulerRegistry#addCronJob` method takes two arguments: a name for the `CronJob`, and the `CronJob` object itself.
 
 > warning **Warning** Remember to inject the `SchedulerRegistry` before accessing it. Import `CronJob` from the `cron` package.
 
-**Delete** a named cron job using the `SchedulerRegistry.deleteCronJob()` method, as follows:
+**Delete** a named cron job using the `SchedulerRegistry#deleteCronJob` method, as follows:
 
 ```typescript
 deleteCron(name: string) {
@@ -288,7 +288,7 @@ deleteCron(name: string) {
 }
 ```
 
-**List** all cron jobs using the `SchedulerRegistry.getCronJobs()` method as follows:
+**List** all cron jobs using the `SchedulerRegistry#getCronJobs` method as follows:
 
 ```typescript
 getCrons() {
@@ -309,7 +309,7 @@ The `getCronJobs()` method returns a `map`. In this code, we iterate over the ma
 
 #### Dynamic intervals
 
-Obtain a reference to an interval with the `SchedulerRegistry.getInterval()` method. As above, inject `SchedulerRegistry` using standard constructor injection:
+Obtain a reference to an interval with the `SchedulerRegistry#getInterval` method. As above, inject `SchedulerRegistry` using standard constructor injection:
 
 ```typescript
 constructor(private schedulerRegistry: SchedulerRegistry) {}
@@ -322,7 +322,7 @@ const interval = this.schedulerRegistry.getInterval('notifications');
 clearInterval(interval);
 ```
 
-**Create** a new interval dynamically using the `SchedulerRegistry.addInterval()` method, as follows:
+**Create** a new interval dynamically using the `SchedulerRegistry#addInterval` method, as follows:
 
 ```typescript
 addInterval(name: string, milliseconds: number) {
@@ -335,10 +335,10 @@ addInterval(name: string, milliseconds: number) {
 }
 ```
 
-In this code, we create a standard JavaScript interval, then pass it to the `ScheduleRegistry.addInterval()` method.
+In this code, we create a standard JavaScript interval, then pass it to the `SchedulerRegistry#addInterval` method.
 That method takes two arguments: a name for the interval, and the interval itself.
 
-**Delete** a named interval using the `SchedulerRegistry.deleteInterval()` method, as follows:
+**Delete** a named interval using the `SchedulerRegistry#deleteInterval` method, as follows:
 
 ```typescript
 deleteInterval(name: string) {
@@ -347,7 +347,7 @@ deleteInterval(name: string) {
 }
 ```
 
-**List** all intervals using the `SchedulerRegistry.getIntervals()` method as follows:
+**List** all intervals using the `SchedulerRegistry#getIntervals` method as follows:
 
 ```typescript
 getIntervals() {
@@ -358,10 +358,10 @@ getIntervals() {
 
 #### Dynamic timeouts
 
-Obtain a reference to a timeout with the `SchedulerRegistry.getTimeout()` method. As above, inject `SchedulerRegistry` using standard constructor injection:
+Obtain a reference to a timeout with the `SchedulerRegistry#getTimeout` method. As above, inject `SchedulerRegistry` using standard constructor injection:
 
 ```typescript
-constructor(private schedulerRegistry: SchedulerRegistry) {}
+constructor(private readonly schedulerRegistry: SchedulerRegistry) {}
 ```
 
 And use it as follows:
@@ -371,7 +371,7 @@ const timeout = this.schedulerRegistry.getTimeout('notifications');
 clearTimeout(timeout);
 ```
 
-**Create** a new timeout dynamically using the `SchedulerRegistry.addTimeout()` method, as follows:
+**Create** a new timeout dynamically using the `SchedulerRegistry#addTimeout` method, as follows:
 
 ```typescript
 addTimeout(name: string, milliseconds: number) {
@@ -384,10 +384,10 @@ addTimeout(name: string, milliseconds: number) {
 }
 ```
 
-In this code, we create a standard JavaScript timeout, then pass it to the `ScheduleRegistry.addTimeout()` method.
+In this code, we create a standard JavaScript timeout, then pass it to the `SchedulerRegistry#addTimeout` method.
 That method takes two arguments: a name for the timeout, and the timeout itself.
 
-**Delete** a named timeout using the `SchedulerRegistry.deleteTimeout()` method, as follows:
+**Delete** a named timeout using the `SchedulerRegistry#deleteTimeout` method, as follows:
 
 ```typescript
 deleteTimeout(name: string) {
@@ -396,7 +396,7 @@ deleteTimeout(name: string) {
 }
 ```
 
-**List** all timeouts using the `SchedulerRegistry.getTimeouts()` method as follows:
+**List** all timeouts using the `SchedulerRegistry#getTimeouts` method as follows:
 
 ```typescript
 getTimeouts() {