nestia 2.1.3 → 2.1.6

package/README.md

@@ -1,60 +1,36 @@
 # Nestia
-Automatic `SDK` and `Swagger` generator for the `NestJS`.
+Automatic `SDK` and `Swagger` generator for the `NestJS`, evolved than ever.
 
 [![GitHub license](https://img.shields.io/badge/license-MIT-blue.svg)](https://github.com/samchon/nestia/blob/master/LICENSE) 
 [![npm version](https://badge.fury.io/js/nestia.svg)](https://www.npmjs.com/package/nestia) 
 [![Downloads](https://img.shields.io/npm/dm/nestia.svg)](https://www.npmjs.com/package/nestia) 
 [![Build Status](https://github.com/samchon/nestia/workflows/build/badge.svg)](https://github.com/samchon/nestia/actions?query=workflow%3Abuild) 
-[![Guide Documents](https://img.shields.io/badge/wiki-documentation-forestgreen)](https://github.com/samchon/nestia/wiki) 
+[![Guide Documents](https://img.shields.io/badge/wiki-documentation-forestgreen)](https://github.com/samchon/nestia/wiki)
 
   - Github: https://github.com/samchon/nestia
-  - NPM: https://www.npmjs.com/packages/nestia
+  - NPM: https://www.npmjs.com/package/nestia
   - Guide Documents: https://github.com/samchon/nestia/wiki
 
-```bash
-# INSTALL NESTIA
-npm install --save-dev nestia
-
-# BUILDING SDK LIBRARY
-npx nestia sdk "src/controller" --out "src/api"
-npx nestia sdk "src/**/*.controller.ts" --out "src/api"
-npx nestia sdk "src/controller" \ 
-    --exclude "src/controller/test" \
-    --out "src/api"
-
-# BUILDING SWAGGER.JSON IS ALSO POSSIBLE
-npx nestia swagger "src/controller" -- out "swagger.json"
-```
-
-Don't write any swagger comment and DTO decorator. Just run the `nestia` up.
-
-  - No swagger comment/decorator
-  - No DTO comment/decorator
-  - Only pure `interface`s and NestJS code are required
-    - Suppors generic typed `interface`s and `controller`s
-    - Support union/intersection types
-    - Support conditional types
+`nestia` is an evolved `SDK` and `Swagger` generator, which analyzes your `NestJS` server code in the compilation level. With `nestia` and compilation level analyzer, you don't need to write any swagger or class-validator decorators. All you need to do is use the `nestia` CLI as shown below.
 
-The `nestia` is an evolved automatic `SDK` and `Swagger` generator than ever, who does not require any type of swagger comment or DTO decorator function, by analyzing your `NestJS` developed backend server code in the compilation level (`nestia` utilizes the TypeScript Compiler API).
-
-Therefore, don't write any swagger comment and don't use any DTO related decorator function. Just use the pure interface type with the pure `NestJS` code. Reading below sections and looking at example codes of the `nestia`, feel how the `nestia` is much stronger than the legacy `@nestjs/swagger`.
+Reading below contents, feel how the "compilation level" makes `nestia` stronger.
 
 Components | `nestia`::SDK | `nestia`::swagger | `@nestjs/swagger`
 -----------|---|---|---
-DTO with pure interface | ✔ | ✔ | ❌
-descriptions by comments | ✔ | ✔ | ❌
+Pure DTO interface | ✔ | ✔ | ❌
+Description comments | ✔ | ✔ | ❌
 Simple structure | ✔ | ✔ | ✔
-Generic typed structure | ✔ | ✔ | ❌
-Union typed structure | ✔ | ✔ | ▲
-Intersection typed structure | ✔ | ✔ | ▲
-Conditional typed structure | ✔ | ▲ | ❌
+Generic type | ✔ | ✔ | ❌
+Union type | ✔ | ✔ | ▲
+Intersection type | ✔ | ✔ | ▲
+Conditional type | ✔ | ▲ | ❌
 Auto completion | ✔ | ❌ | ❌
 Type hints | ✔ | ❌ | ❌
 2x faster `JSON.stringify()` | ✔ | ❌ | ❌
-Ensure type safety | ✔ | ❌ | ❌
+Ensure type safety | ✅ | ❌ | ❌
 
 ```typescript
-// IMPORT SDK LIBRARY WHO'VE BEEN GENERATED BY THE NESTIA
+// IMPORT SDK LIBRARY GENERATED BY NESTIA
 import api from "@samchon/shopping-api";
 import { IPage } from "@samchon/shopping-api/lib/structures/IPage";
 import { ISale } from "@samchon/shopping-api/lib/structures/ISale";
@@ -112,14 +88,44 @@ export async function trace_sale_question_and_comment
 
 
 
+## Setup
+Just like any other package, you've got to install it before you can use it.
+
+```sh
+npm install --save-dev nestia
+```
+
+After the installation, you can generate the `SDK` or `Swagger`, directly.
+
+```sh
+npx nestia sdk "src/**/*.controller" --out "src/api"
+npx nestia swagger "src/**/*.controller" --out "swagger.json"
+```
+
+> If all of your controller files are gathered into one directory:
+>
+> ```sh
+> npx nestia sdk "src/controllers" --out "src/api"
+> npx nestia swagger "src/controllers" --out "swagger.json"
+> ```
+> 
+> You can omit all of the parameters if you've configured the [nestia.config.ts](#configuration) file.
+> 
+> ```sh
+> npx nestia sdk
+> npx nestia swagger
+> ```
+
+
+
 
 ## Demonstrations
 ### Pure DTO Interface
-The `nestia` can utilize the pure interface type as DTO.
+`nestia` can utilize pure interface type as DTO.
 
-Unlike the legacy `@nestjs/swagger` who requires a class with decorator functions when defining the DTO, the `nestia` can use the pure interface directly. Also, `nestia` can use the descriptive comments of the pure DTO interface, too.
+Unlike `@nestjs/swagger` which requires the DTO class with decorators, `nestia` can use the pure interface type directly. Also, `nestia` can utilize the pure descriptive comments, instead of using the `description` property of the decorators. Furthermore, `nestia` can even support generic types, union/intersection types and even conditional types.
 
-Furthermore, as the `nestia` can use the pure interface type directly, it's possible to define a generic typed DTO interface with inheritance. Of course, using alis type or union typed DTO are also possibble, too. Besides, `@nestjs/swagger` never can construct such generic typed DTO and constructing union typed DTO is possible but extremely difficult.
+Look at the code below, you may see the difference between `nestia` and `@nestjs/swagger`, and thereby catch the meaning of the pure DTO interface.
 
   - Simple [`ISaleArticleComment`](https://github.com/samchon/nestia/tree/master/demo/simple/src/api/structures/ISaleArticleComment.ts)
   - Generic interfaces
@@ -127,15 +133,77 @@ Furthermore, as the `nestia` can use the pure interface type directly, it's poss
     - parent interface, [`ISaleInquiry<Content>`](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/structures/ISaleInquiry.ts)
     - 1st sub-type interface, [`ISaleQuestion`](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/structures/ISaleQuestion.ts)
     - 2nd sub-type interface, [`ISaleReview`](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/structures/ISaleReview.ts)
-  - Union alias type [`ISaleEntireArticle`](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/structures/ISaleArticle.ts)
-
-Looking at the below example code, then you may understand which differences between the `nestia` and `@nestjs/swagger` and what the pure interface DTO type means. Writing the legacy DTO class of the `@nestjs/swagger` after a very long time, I felt the feeling again, "this is insane". 
+  - Union alias type [`ISaleEntireArticle`](https://github.com/samchon/nestia/tree/master/demo/union/src/api/structures/ISaleEntireArticle.ts)
 
 > The below example code would be shown by clicking the arrow button or text.
 
 <details>
     <summary>
-        Pure DTO interface, of the <code>nestia</code>
+        Traditional DTO class using <code>@nestjs/swagger</code>
+    </summary>
+
+```typescript
+export class SaleArticleComment
+{
+    @ApiProperty({
+        description: 
+`Comment wrote on a sale related article.
+
+When an article of a sale has been enrolled, all of the participants like consumers and sellers can write a comment on that article. However, when the writer is a consumer, the consumer can hide its name through the annoymous option.
+
+Also, writing a reply comment for a specific comment is possible and in that case, the ISaleArticleComment.parent_id property would be activated.`
+    })
+    id: number;
+
+    @ApiProperty({
+        type: "number",
+        nullable: true,
+        description:
+`Parent comment ID.
+
+Only When this comment has been written as a reply.`
+    })
+    parent_id: number | null;
+
+    @ApiProperty({
+        type: "string",
+        description: "Type of the writer."
+    })
+    writer_type: "seller" | "consumer";
+
+    @ApiProperty({
+        type: "string",
+        nullable: true,
+        description:
+`Name of the writer.
+
+When this is a type of anonymous comment, writer name would be hidden.`
+    })
+    writer_name: string | null;
+
+    @ApiProperty({
+        type: "array",
+        items: {
+            schema: { $ref: getSchemaPath(SaleArticleComment.Content) }
+        },
+        description:
+`Contents of the comments.
+
+When the comment writer tries to modify content, it would not modify the comment content but would be accumulated Therefore, all of the people can read how the content has been changed.`
+    })
+    contents: SaleArticleComment.Content[];
+
+    @ApiProperty({
+        description: "Creation time."
+    })
+    created_at: string;
+}
+```
+</details>
+
+<details>
+    <summary>
+        Pure DTO interface using <code>nestia</code>
     </summary>
 
 ```typescript
@@ -235,79 +303,116 @@ export namespace ISaleArticleComment
 
 <details>
     <summary>
-        Legacy DTO class, of the <code>@nestjs/swagger</code>
+        Generic typed DTO using <code>nestia</code>
     </summary>
 
 ```typescript
-export class SaleArticleComment
+/**
+ * Inquiry article.
+ * 
+ * Sub-type of article and super-type of question and answer.
+ * 
+ *  - List of the sub-types
+ *    - {@link ISaleQuestion}
+ *    - {@link ISaleReview}
+ * 
+ * @template Content Content type
+ * @author Jeongho Nam - https://github.com/samchon
+ */
+export interface ISaleInquiry<Content extends ISaleInquiry.IContent> 
+    extends ISaleArticle<Content> 
 {
-    @ApiProperty({
-        description: 
-`Comment wrote on a sale related article.
-
-When an article of a sale has been enrolled, all of the participants like consumers and sellers can write a comment on that article. However, when the writer is a consumer, the consumer can hide its name through the annoymous option.
-
-Also, writing a reply comment for a specific comment is possible and in that case, the ISaleArticleComment.parent_id property would be activated.`
-    })
+    /**
+     * Primary Key.
+     */
     id: number;
 
-    @ApiProperty({
-        type: "number",
-        nullable: true,
-        description:
-`Parent comment ID.
-
-Only When this comment has been written as a reply.`
-    })
-    parent_id: number | null;
+    /**
+     * Name of the writer.
+     */
+    writer: string;
 
-    @ApiProperty({
-        type: "string",
-        description: "Type of the writer."
-    })
-    writer_type: "seller" | "consumer";
+    /**
+     * List of contents.
+     * 
+     * When the article writer tries to modify content, it would not modify the article
+     * content but would be accumulated. Therefore, all the people can read how
+     * the content has been changed.
+     */
+    contents: Content[];
 
-    @ApiProperty({
-        type: "string",
-        nullable: true,
-        description:
-`Name of the writer.
+    /**
+     * Creation time.
+     */
+    createdAat: string;
+        
+    /**
+     * Formal answer from the seller.
+     */
+    answer: ISaleInquiryAnswer | null;
+}
+export namespace ISaleInquiry 
+{
+    /**
+     * Content info.
+     */
+    export interface IContent 
+    {
+        /**
+         * Primary Key
+         */
+        id: string;
 
-When this is a type of anonymous comment, writer name would be hidden.`
-    })
-    writer_name: string | null;
+        /**
+         * Title of the content.
+         */
+        title: string;
 
-    @ApiProperty({
-        type: "array",
-        items: {
-            schema: { $ref: getSchemaPath(SaleArticleComment.Content) }
-        },
-        description:
-`Contents of the comments.
+        /**
+         * Body of the content.
+         */
+        body: string;
 
-When the comment writer tries to modify content, it would not modify the comment content but would be accumulated Therefore, all of the people can read how the content has been changed.`
-    })
-    contents: SaleArticleComment.Content[];
+        /**
+         * Attached files.
+         */
+        files: IAttachmentFile[];
 
-    @ApiProperty({
-        description: "Creation time."
-    })
-    created_at: string;
+        /**
+         * Creation time.
+         */
+        createdAt: string;
+    }
 }
 ```
 </details>
 
+<details>
+    <summary>
+        Union typed DTO using <code>nestia</code>
+    </summary>
+
+```typescript
+/**
+ * Union type of the entire sub-type articles.
+ * 
+ * @author Jeongho Nam - https://github.com/samchon
+ */
+export type ISaleEntireArtcle = ISaleQuestion | ISaleReview;
+```
+</details>
+
 
 
 
 ### Advanced Controller Class
 Controller also can use the generic arguments.
 
-In the previous [Pure DTO Interface](#pure-dto-interface) corner, we've learned that the `nestia` can use the pure interface type as the DTO. Also, we've learned that using the pure interface type as DTO means that making generic typed interface or union typed interface as the DTO are also possible, too.
+In the previous [Pure DTO Interface](#pure-dto-interface) corner, we've learned that `nestia` can use the pure interface type as DTO. Also, we've learned that utilizing generic, union/intersection and even conditional typed interfaces are also possible.
 
-In the Controller case, it's the same with the upper interface story. In the `nestia`, as using generic typed interface as DTO was possible, defining generic typed controller class is also possible, too. By defining the generic typed controller class as the super type class, you can extremely reduce both duplicated code and duplicated description comments.
+In the Controller case, it's same with the upper DTO story. With `nestia`, defining a generic typed controller class is also possible, too. By defining a generic typed controller class as a super-type class, you can reduce both duplicated code and description comments.
 
-Look at the below code and feel how the `nestia` is powerful. I repeat that, `@nestjs/swagger` never can construct such generic or union typed controller classes, either.
+Look at the below code and feel how powerful `nestia` is. It should be stated that, `@nestjs/swagger` cannot construct such generic or union typed controller class.
 
   - Simple [`CustomerSaleArticleCommentsController`](https://github.com/samchon/nestia/blob/master/demo/simple/src/controllers/ConsumerSaleArticleCommentsController.ts)
   - Generic controllers
@@ -316,6 +421,26 @@ Look at the below code and feel how the `nestia` is powerful. I repeat that, `@n
     - 2nd sub-type controller, [`ConsumerSaleQuestionsController`](https://github.com/samchon/nestia/tree/master/demo/generic/src/controllers/ConsumerSaleQuestionsController.ts)
   - Union controller, [`ConsumerSaleEntireArticlesController`](https://github.com/samchon/nestia/tree/master/demo/union/src/controllers/ConsumerSaleEntireArticlesController.ts)
 
+> [typescript-is](https://github.com/woutervh-/typescript-is) can replace the class-validator with only one line.
+> 
+> ```typescript
+> import * as nest from "@nestjs/common";
+> import { assertType } from "typescript-is";
+>
+> @nest.Controller("consumers/:section/sales/:saleId/questions")
+> export class SaleQuestionsController
+>     extends SaleInquiriesController<
+>         ISaleQuestion,
+>         ISaleQuestion.IContent,
+>         ISaleQuestion.IStore> 
+> {
+>     public constructor() 
+>     {
+>         super(input => assertType<ISaleQuestion.IStore>(input));
+>     }
+> }
+> ```
+
 ```typescript
 import * as express from "express";
 import * as nest from "@nestjs/common";
@@ -328,6 +453,11 @@ export abstract class SaleInquiriesController<
         Store extends ISaleInquiry.IStore,
         Json extends ISaleInquiry<Content>>
 {
+    /**
+     * Constructor with type assert function.
+     */
+    protected constructor(private readonly assert: (input: Store) => void);
+
     /**
      * Store a new inquiry.
      * 
@@ -385,19 +515,19 @@ export abstract class SaleInquiriesController<
 
 
 ### Software Development Kit
-> `Swagger` is torturing the client developers.
+> `Swagger` is torturing client developers.
 >
-> If you're a backend developer and you deliver a `Swagger` to your companion client developers, the client developers should analyze the `Swagger` and implement duplicated router functions with DTO interfaces by themselves. During those jobs, if the client developers take a mistake by mis-reading the `Swagger`, it becomes the critical runtime error directly.
+> If you're a backend developer and you deliver a `Swagger` to your companion client developers, they should analyze the `Swagger` and implement duplicated router functions with DTO interfaces by themselves. During those jobs, if a client developer takes a mistake by mis-reading the `Swagger`, it becomes a critical runtime error directly.
 >
-> Why do you torture the client developers such like that? If you deliver an SDK (Software Development Kit) instead of the `Swagger`, the client developers don't need to read the `Swagger` file and don't need to implement the duplicated DTO interfaces and router functions, either.
+> Why are you torturing the client developers such like that? If you deliver an SDK (Software Development Kit) instead of the `Swagger`, the client developers don't need to read the `Swagger` file. They never need to implement the duplicated DTO interfaces with router functions, either.
 >
-> Therefore, just build the SDK through this `nestia` and delivers the SDK. Your client developers would be anticipated from the long time torturing and become happy. Your solution would be much more reliable and efficient, too.
+> Therefore, just build the SDK through this `nestia` and deliver the SDK. Your client developers would be anticipated from the long time torturing and become happy. Your solution would be much more reliable and efficient, too.
 
-Looking at the SDK library file, generated by the `nestia`, it seems perfect.
+Looking at the SDK library file, generated by `nestia`, it is perfect.
 
-Exact route method, path and parameters are constructed and DTO structures are perfectly imported. Also, descriptive comments written on the controller class methods, DTO interfaces and their properties are exactly revied in the SDK library.
+Route method, path and parameters are well-formed and DTO structures are correctly imported. Also, descriptive comments are fully revived in the SDK library, regardless of where they are written.
 
-Furthermore, there's not any problem even when the generic typed abstract controller classes with generic typed DTO comes. The `nestia` will specialize the generic arguments exactly, by analyzing your `NestJS` developed backend server code, in the compilation level.
+Furthermore, there's not any problem even when a generic typed controller class comes. `nestia` will specialize the generic arguments exactly, by analyzing your `NestJS` server code, in the compilation level.
 
   - [simple/.../comments/index.ts](https://github.com/samchon/nestia/blob/master/demo/simple/src/api/functional/consumers/sales/articles/comments/index.ts)
   - [generic/.../questions/index.ts](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/functional/consumers/sales/questions/index.ts)
@@ -540,11 +670,9 @@ export namespace update
 ### Swagger
 Building `Swagger` is also possible and even much powerful.
 
-Although I think the `Swagger` is a typical tool that torturing the client developers, the `nestia` also can build the `swagger.json` file. Even `Swagger` generator of the `nestia` is much powerful and convenient than the `@nestjs/swagger`. It doesn't require any type of the swagger comment or DTO decorator function and just using the pure interface type as DTO is possible.
-
-Looking at the [simple/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fsimple%2Fswagger.json) file, generated by the `nestia`, it seems perfect. Exact route method, path and parameters are constructed and DTO structures are exactly same with the pure interace type `ISaleArticleComment`. Also, comments written on the controller class method, DTO interface `ISaleArticleComment` and its properties are exactly revied on the `description` fields in the `swagger.json`.
+Looking at the [simple/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fsimple%2Fswagger.json) file, generated by `nestia`, everything is perfect. Route method, path and parameters are well-formed. Also, schema definitions are exactly matched with the pure interface type `ISaleArticleComment`. Of course, descriptive comments are perfectly resurrected in the `description` properties of the `swagger.json` file.
 
-Looking at the another file [generic/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fgeneric%2Fswagger.json), you can find that there isn't any problem even when the generic typed DTO interfaces or controller classes come. Furthermore, traveling the `description` properties of the [generic/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Funion%2Fswagger.json), comments written on the generic interfaces and controllers are exactly revived in each route functions and schema definitions.
+Looking at the another file [generic/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fgeneric%2Fswagger.json), you can find that there isn't any problem even when a generic typed DTO and controller come. The last file [union/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Funion%2Fswagger.json), there's no problem on the union type, either.
 
   - View in the `Swagger Editor`
     - [simple/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fsimple%2Fswagger.json)
@@ -565,29 +693,34 @@ SDK Generation               | ✔  | ✔  | ❌
 Type check in runtime        | ✔  | ❌ | ❌
 Custom compiler options      | ✔  | ❌ | ❌
 
-You can configure the nestia builder options by two ways: `CLI` or `configuration file`.
+`nestia` can configure generator options by two ways: CLI and configuration file.
 
-The CLI (Command Line Interface) is easy to use, because it does not require any type of configuration file wrinting. However, it's not safe thing that repeating the same command whenever generating the SDK or `swagger.json` through the CLI, because command miswriting can be happened.
+At first, the CLI (Command Line Interface) is convenient, but does not support detailed options.
 
-```bash
+```sh
 # BASIC COMMAND
-npx nestia <nestia|swagger> <source_directories_or_patterns> \
+npx nestia <sdk|swagger> <source_directories_or_patterns> \
     --exclude <exclude_directory_or_pattern> \
     --out <output_directory_or_file>
 
 # EXAMPLES
-npx nestia nestia "src/controllers" --out "src/api"
-npx nestia swagger "src/**/*.controller.ts" -- out "swagger.json"
+npx nestia sdk "src/controllers" --out "src/api"
+npx nestia swagger "src/**/*.controller.ts" --out "swagger.json"
 npx nestia swagger "src/main/controllers" "src/sub/controllers" \
     --exclude "src/main/test" \
     --out "composite.swagger.json"
 
 # ONLY WHEN NESTIA.CONFIG.TS EXISTS
-npx nestia nestia
+npx nestia sdk
 npx nestia swagger
 ```
 
-Otherwise, configuration file `nestia.config.ts` may hard to construct and the construction would be annoying and inconvenient, such configuration would be useful within framework of the reusability. Also, the configuration file `nestia.config.ts` use much detailed options than the `CLI` and its content can be ensured its safety by TypeScript compiler through the `IConfigruation` interface type.
+Besides, the configuration file `nestia.config.ts` supports much detailed options. 
+
+The detailed options are listed up to the `IConfiguration` interface. You can utilize the `IConfiguration` type like below. If you want to know more about those options, please check the [Guide Documents](https://github.com/samchon/nestia/wiki/Configuration).
+
+<details>
+    <summary> Read <code>IConfiguration</code> </summary>
 
 ```typescript
 /**
@@ -595,10 +728,9 @@ Otherwise, configuration file `nestia.config.ts` may hard to construct and the c
  * 
  * @author Jeongho Nam - https://github.com/samchon
  */
-export interface IConfiguration
-{
+export interface IConfiguration {
     /**
-     * List of files or directories containing the NestJS controller classes.
+     * List of files or directories containing the `NestJS` controller classes.
      */
     input: string | string[] | IConfiguration.IInput;
 
@@ -660,13 +792,12 @@ export interface IConfiguration
 export namespace IConfiguration
 {
     /**
-     * List of files or directories to include or exclude to specifying the NestJS 
+     * List of files or directories to include or exclude to specifying the `NestJS` 
      * controllers.
      */
-    export interface IInput
-    {
+    export interface IInput {
         /**
-         * List of files or directories containing the NestJS controller classes.
+         * List of files or directories containing the `NestJS` controller classes.
          */
         include: string[];
 
@@ -679,8 +810,7 @@ export namespace IConfiguration
     /**
      * Building `swagger.json` is also possible.
      */
-    export interface ISwagger
-    {
+    export interface ISwagger {
         /**
          * Output path of the `swagger.json`.
          * 
@@ -692,8 +822,7 @@ export namespace IConfiguration
     }
 }
 ```
-
-When you've completed to reading the `IConfiguration` interface, let's make the `nestia.config.ts` file directly. At first, move to your project directory. Note that the project directory means the top level directory of your project, where configuration files like `package.json` or `tsconfig.json` are placed in. After the movement, make the new `nestia` configuration file and write some script like below:
+</details>
 
 ```typescript
 import type { IConfiguration } from "nestia";
@@ -714,18 +843,7 @@ export default NESTIA_CONFIG;
 
 ## Appendix
 ### Dependencies of the SDK
-An SDK library generated by the `nestia` requires the [nestia-fetcher](https://github.com/samchon/nestia-fetcher) module. Also, the [typescript-is](https://github.com/woutervh-/typescript-is) and [typescript-json](https://github.com/samchon/typescript-json) modules can be required following your nestia.config.ts options.
-
-```json
-{
-  "name": "payments-server-api",
-  "dependencies": {
-    "nestia-fetcher": "^2.0.1",
-    "typescript-is": "^0.19.0",
-    "typescript-json": "^2.0.9"
-  }
-}
-```
+An SDK library generated by `nestia` requires [nestia-fetcher](https://github.com/samchon/nestia-fetcher) module. Also, [typescript-is](https://github.com/woutervh-/typescript-is) and [typescript-json](https://github.com/samchon/typescript-json) modules can be required following your `nestia.config.ts` configuration file.
 
 The `npx nestia install` command installs those dependencies with the `package.json` configuration.
 
@@ -742,7 +860,7 @@ https://github.com/samchon/backend
 
 I support template backend project using this `nestia` library, `samchon/backend`.
 
-Reading the README content of the backend template repository, you can find lots of example backend projects who've been generated from the backend. Furthermore, those example projects guide how to generate SDK library from the `nestia` and how to distribute the SDK library thorugh the NPM module.
+Reading the README content of the backend template repository, you can find lots of example backend projects who've been generated from the backend. Furthermore, those example projects guide how to generate SDK library from `nestia` and how to distribute the SDK library thorugh the NPM module.
 
 Therefore, if you're planning to compose your own backend project using this `nestia`, I recommend you to create the repository and learn from the `samchon/backend` template project.
 
@@ -762,4 +880,4 @@ The Archidraw is a great IT company developing 3D interior editor and lots of so
 > - 회사소개서: [archidraw.pdf](https://github.com/archidraw/payments/files/7696710/archidraw.pdf)
 > - 기술 스택: React + TypeScript
 > - 이력서: 자유 양식
-> - 지원처: samchon@archisketch.com
+> - 지원처: samchon@archisketch.com

package/lib/analyses/ControllerAnalyzer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ControllerAnalyzer.d.ts","sourceRoot":"","sources":["../../src/analyses/ControllerAnalyzer.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,YAAY,CAAC;AAG5B,OAAO,EAAE,WAAW,EAAE,MAAM,2BAA2B,CAAC;AACxD,OAAO,EAAE,MAAM,EAAE,MAAM,sBAAsB,CAAC;AAM9C,yBAAiB,kBAAkB,CACnC;IACI,SAAgB,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC,UAAU,EAAE,UAAU,EAAE,WAAW,GAAG,MAAM,EAAE,CAc7G;CAqJJ"}
+{"version":3,"file":"ControllerAnalyzer.d.ts","sourceRoot":"","sources":["../../src/analyses/ControllerAnalyzer.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,YAAY,CAAC;AAG5B,OAAO,EAAE,WAAW,EAAE,MAAM,2BAA2B,CAAC;AACxD,OAAO,EAAE,MAAM,EAAE,MAAM,sBAAsB,CAAC;AAM9C,yBAAiB,kBAAkB,CACnC;IACI,SAAgB,OAAO,CAAC,OAAO,EAAE,EAAE,CAAC,WAAW,EAAE,UAAU,EAAE,EAAE,CAAC,UAAU,EAAE,UAAU,EAAE,WAAW,GAAG,MAAM,EAAE,CAc7G;CA+JJ"}

package/lib/analyses/ControllerAnalyzer.js

@@ -93,8 +93,8 @@ var ControllerAnalyzer;
             var runtime = controller.functions.find(function (f) { return f.name === identifier.escapedText; });
             if (runtime === undefined)
                 return "continue";
-            var route = _Analyze_function(checker, controller, genericDict, runtime, property);
-            ret.push(route);
+            var routes = _Analyze_function(checker, controller, genericDict, runtime, property);
+            ret.push.apply(ret, __spreadArray([], __read(routes), false));
         };
         try {
             for (var _b = __values(classType.getProperties()), _c = _b.next(); !_c.done; _c = _b.next()) {
@@ -115,6 +115,7 @@ var ControllerAnalyzer;
         FUNCTION
     --------------------------------------------------------- */
     function _Analyze_function(checker, controller, genericDict, func, symbol) {
+        var e_2, _a, e_3, _b;
         // PREPARE ASSETS
         var type = checker.getTypeOfSymbolAtLocation(symbol, symbol.valueDeclaration);
         var signature = checker.getSignaturesOfType(type, typescript_1.default.SignatureKind.Call)[0];
@@ -127,12 +128,38 @@ var ControllerAnalyzer;
         var imports = importDict
             .toJSON()
             .map(function (pair) { return [pair.first, pair.second.toJSON()]; });
-        // CONFIGURE PATH
-        var path = _Normalize_path(path_1.default.join(controller.path, func.path)
-            .split("\\")
-            .join("/"));
+        // CONSTRUCT COMMON DATA
+        var common = __assign(__assign({}, func), { parameters: parameters, output: output, imports: imports, symbol: "".concat(controller.name, ".").concat(func.name, "()"), comments: signature.getDocumentationComment(undefined), tags: signature.getJsDocTags() });
+        // CONFIGURE PATHS
+        var pathList = [];
+        try {
+            for (var _c = __values(controller.paths), _d = _c.next(); !_d.done; _d = _c.next()) {
+                var controllerPath = _d.value;
+                try {
+                    for (var _e = (e_3 = void 0, __values(func.paths)), _f = _e.next(); !_f.done; _f = _e.next()) {
+                        var filePath = _f.value;
+                        var path = path_1.default.join(controllerPath, filePath).split("\\").join("/");
+                        pathList.push(_Normalize_path(path));
+                    }
+                }
+                catch (e_3_1) { e_3 = { error: e_3_1 }; }
+                finally {
+                    try {
+                        if (_f && !_f.done && (_b = _e.return)) _b.call(_e);
+                    }
+                    finally { if (e_3) throw e_3.error; }
+                }
+            }
+        }
+        catch (e_2_1) { e_2 = { error: e_2_1 }; }
+        finally {
+            try {
+                if (_d && !_d.done && (_a = _c.return)) _a.call(_c);
+            }
+            finally { if (e_2) throw e_2.error; }
+        }
         // RETURNS
-        return __assign(__assign({}, func), { path: path, parameters: parameters, output: output, imports: imports, symbol: "".concat(controller.name, ".").concat(func.name, "()"), comments: signature.getDocumentationComment(undefined), tags: signature.getJsDocTags() });
+        return pathList.map(function (path) { return (__assign(__assign({}, common), { path: path })); });
     }
     function _Normalize_path(path) {
         if (path[0] !== "/")

package/lib/analyses/ReflectAnalyzer.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"ReflectAnalyzer.d.ts","sourceRoot":"","sources":["../../src/analyses/ReflectAnalyzer.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,WAAW,EAAE,MAAM,2BAA2B,CAAC;AAQxD,yBAAiB,eAAe,CAChC;IACI,SAAsB,OAAO,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,CAAC,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,CAiBxF;CAsMJ"}
+{"version":3,"file":"ReflectAnalyzer.d.ts","sourceRoot":"","sources":["../../src/analyses/ReflectAnalyzer.ts"],"names":[],"mappings":"AAMA,OAAO,EAAE,WAAW,EAAE,MAAM,2BAA2B,CAAC;AAQxD,yBAAiB,eAAe,CAChC;IACI,SAAsB,OAAO,CAAC,MAAM,EAAE,OAAO,CAAC,GAAG,CAAC,EAAE,IAAI,EAAE,MAAM,GAAG,OAAO,CAAC,WAAW,EAAE,CAAC,CAiBxF;CAqNJ"}