nestia 2.1.2 → 2.1.5

package/README.md

@@ -1,373 +1,474 @@
 # Nestia
-Automatic `SDK` and `swagger.json` generator for the NestJS.
-
-[![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)
-
-```bash
-# INSTALL NESTIA
-npm install --save-dev nestia
-
-# WHEN ALL OF THE CONTROLLRES ARE GATHERED INTO A DIRECTORY
-npx nestia sdk "src/controller" --out "src/api"
-
-# REGULAR NESTJS PATTERN
-npx nestia sdk "src/**/*.controller.ts" --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](https://github.com/samchon/nestia) up.
-
-  - No swagger comment/decorator
-  - No DTO comment/decorator
-  - Only pure NestJS code is required
-  - [Guide Documents (Wiki)](https://github.com/samchon/nestia/wiki), if you want to know more
-
-When you're developing a backend server using the `NestJS`, you don't need any extra dedication, for delivering the Rest API to the client developers, like writing the `swagger` comments or DTO decorators. 
-
-You just run this [nestia](https://github.com/samchon/nestia) up, then [nestia](https://github.com/samchon/nestia) would generate the SDK automatically, by analyzing your controller classes in the compliation and runtime level. With the automatically generated SDK through this [nestia](https://github.com/samchon/nestia), client developer also does not need any extra work, like reading `swagger` and writing the duplicated interaction code. Client developer only needs to import the SDK and calls matched function with the `await` symbol.
-
-> Even generating the `swagger.json` without any swagger comment and DTO decorator is also possible. When generating the `swagger.json`, no DTO comment and decorator is required, either. Use only the pure interface definitions.
+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)
+
+  - Github: https://github.com/samchon/nestia
+  - NPM: https://www.npmjs.com/packages/nestia
+  - Guide Documents: https://github.com/samchon/nestia/wiki
+
+`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.
+
+Reading below contents, feel how the "compilation level" makes `nestia` stronger.
+
+Components | `nestia`::SDK | `nestia`::swagger | `@nestjs/swagger`
+-----------|---|---|---
+Pure DTO interface | ✔ | ✔ | ❌
+Description comments | ✔ | ✔ | ❌
+Simple structure | ✔ | ✔ | ✔
+Generic type | ✔ | ✔ | ❌
+Union type | ✔ | ✔ | ▲
+Intersection type | ✔ | ✔ | ▲
+Conditional type | ✔ | ▲ | ❌
+Auto completion | ✔ | ❌ | ❌
+Type hints | ✔ | ❌ | ❌
+2x faster `JSON.stringify()` | ✔ | ❌ | ❌
+Ensure type safety | ✅ | ❌ | ❌
 
 ```typescript
-import api from "@samchon/bbs-api";
-import { IBbsArticle } from "@samchon/bbs-api/lib/structures/bbs/IBbsArticle";
-import { IPage } from "@samchon/bbs-api/lib/structures/common/IPage";
-
-export async function test_article_read(connection: api.IConnection): Promise<void>
+// 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";
+import { ISaleArticleComment } from "@samchon/shopping-api/lib/structures/ISaleArticleComment";
+import { ISaleQuestion } from "@samchon/shopping-api/lib/structures/ISaleQuestion";
+
+export async function trace_sale_question_and_comment
+    (connection: api.IConnection): Promise<void>
 {
-    // LIST UP ARTICLE SUMMARIES
-    const index: IPage<IBbsArticle.ISummary> = await api.functional.bbs.articles.index
+    // LIST UP SALE SUMMARIES
+    const index: IPage<ISale.ISummary> = await api.functional.shoppings.sales.index
     (
         connection,
-        "free",
+        "general",
         { limit: 100, page: 1 }
     );
 
-    // READ AN ARTICLE DETAILY
-    const article: IBbsArticle = await api.functional.bbs.articles.at
+    // PICK A SALE
+    const sale: ISale = await api.functional.shoppings.sales.at
     (
-        connection,
-        "free",
+        connection, 
         index.data[0].id
     );
-    console.log(article.title, aritlce.body, article.files);
+    console.log("sale", sale);
+
+    // WRITE A QUESTION
+    const question: ISaleQuestion = await api.functional.shoppings.sales.questions.store
+    (
+        connection,
+        "general",
+        sale.id,
+        {
+            title: "How to use this product?",
+            body: "The description is not fully enough. Can you introduce me more?",
+            files: []
+        }
+    );
+    console.log("question", question);
+
+    // WRITE A COMMENT
+    const comment: ISaleArticleComment = await api.functional.shoppings.sales.comments.store
+    (
+        connection,
+        "general",
+        sale.id,
+        question.id,
+        {
+            body: "p.s) Can you send me a detailed catalogue?",
+            anonymous: false
+        }
+    );
+    console.log("comment", comment);
 }
 ```
 
 
 
+## Setup
+Just like any other package, you've got to install it before you can use it.
 
-## Usage
-### Installation
-```bash
+```sh
 npm install --save-dev nestia
 ```
 
-Installing the [nestia](https://github.com/samchon/nestia) is very easy.
+After the installation, you can generate the `SDK` or `Swagger`, directly.
 
-Just type the `npm install --save-dev nestia` command in your NestJS backend project.
+```sh
+npx nestia sdk "src/**/*.controller" --out "src/api"
+npx nestia swagger "src/**/*.controller" --out "swagger.json"
+```
 
-### SDK generation
-```bash
-npx nestia sdk <source_controller_directory> --out <output_sdk_directory>
+> 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
+> ```
 
-npx nestia sdk "src/**/*.controller.ts" --out "src/api"
-npx nestia sdk "src/controllers" --out "src/api"
-npx nestia sdk "src/controllers/consumers" "src/controllers/sellers" --out "src/api"
-npx nestia sdk "src/controllers" --exclude "src/**/Fake*.ts" --out "src/api"
-```
 
-To generate a SDK library through the [nestia](https://github.com/samchon/nestia) is very easy. 
 
-Just type the `nestia sdk <input> --out <output>` command in the console. When there're multiple source directories containing the NestJS controller classes, type all of them separating by a `space` word. If you want to exclude some directories or files from the SDK generation, the `--exclude` option would be useful.
 
-Also, when generating a SDK using the cli options, `compilerOptions` would follow the `tsconfig.json`, that is configured for the backend server. If no `tsconfig.json` file exists in your project, the configuration would be default option (`ES5` with `strict` mode). If you want to use different `compilerOptions` with the `tsconfig.json`, you should configure the [nestia.config.ts](#nestiaconfigts).
+## Demonstrations
+### Pure DTO Interface
+`nestia` can utilize pure interface type as DTO.
 
-### Swagger generation
-```bash
-npx nestia <source_controller_of_directory> --out <output_path>
+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.
 
-npx nestia swagger "src/**/*.controller.ts" --out "./"
-npx nestia swagger "src/controllers" --out "./swagger.json"
-npx nestia swagger "src/consumers" "src/sellers" --out "actors.json"
-npx nestia swagger "src/controllers" --exclude "src/**/Fake*.ts" -out "./" 
-```
+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.
 
-The [nestia](https://github.com/samchon/nestia) even supports the `swagger.json` generation and it's also extermely easy.
+  - Simple [`ISaleArticleComment`](https://github.com/samchon/nestia/tree/master/demo/simple/src/api/structures/ISaleArticleComment.ts)
+  - Generic interfaces
+    - grandparent interface, [`ISaleArticle<Content>`](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/structures/ISaleArticle.ts)
+    - 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/union/src/api/structures/ISaleEntireArticle.ts)
 
-Jsut type the `nestia swagger <input> --out <output>` command in the console. When there're multiple source directories containing the NestJS controller classes, type all of them separating by a `space` word. If you want to exclude some directories or files from the `swagger.json` generation, the `--exclude` option would be useful.
+> The below example code would be shown by clicking the arrow button or text.
 
-Also, when generating a SDK using the cli options, `compilerOptions` would follow the `tsconfig.json`, that is configured for the backend server. If no `tsconfig.json` file exists in your project, the configuration would be default option (`ES5` with `strict` mode). If you want to use different `compilerOptions` with the `tsconfig.json`, you should configure the [nestia.config.ts](#nestiaconfigts).
+<details>
+    <summary>
+        Traditional DTO class using <code>@nestjs/swagger</code>
+    </summary>
 
-### Dependencies
-```bash
-npx nestia install
-```
+```typescript
+export class SaleArticleComment
+{
+    @ApiProperty({
+        description: 
+`Comment wrote on a sale related article.
 
-SDK library generated by the [nestia](https://github.com/samchon/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](#nestiaconfigts) options.
+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.
 
-The `npx nestia install` command installs those dependencies with `package.json` configuration.
+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;
 
-```json
-{
-  "name": "payments-server-api",
-  "dependencies": {
-    "nestia-fetcher": "^2.0.1",
-    "typescript-is": "^0.19.0",
-    "typescript-json": "^2.0.9"
-  }
+    @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>
 
-
-## Advanced
-### `nestia.config.ts`
 ```typescript
 /**
- * Definition for the `nestia.config.ts` file.
+ * 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 
+ * {@link ISaleArticleComment.parent_id} property would be activated.
  * 
  * @author Jeongho Nam - https://github.com/samchon
  */
-export interface IConfiguration
+export interface ISaleArticleComment
 {
     /**
-     * List of files or directories containing the NestJS controller classes.
+     * Primary Key.
      */
-    input: string | string[] | IConfiguration.IInput;
+    id: number;
 
     /**
-     * Output directory that SDK would be placed in.
+     * Parent comment ID.
+     * 
+     * Only When this comment has been written as a reply.
      */
-    output?: string;
+    parent_id: number | null;
 
     /**
-     * Compiler options for the TypeScript.
-     * 
-     * If omitted, the configuration would follow the `tsconfig.json`.
+     * Type of the writer.
      */
-    compilerOptions?: ts.CompilerOptions;
+    writer_type: "seller" | "consumer";
 
     /**
-     * Whether to assert parameter types or not.
+     * Name of the writer.
      * 
-     * If you configure this option to be `true`, all of the function parameters would be
-     * checked through the [typescript-is](https://github.com/woutervh-/typescript-is).
+     * When this is a type of anonymous comment, writer name would be hidden.
      */
-    assert?: boolean;
+    writer_name: string | null;
 
     /**
-     * Whether to optimize JSON string conversion 2x faster or not.
+     * Contents of the comments.
      * 
-     * If you configure this option to be `true`, the SDK library would utilize the
-     * [typescript-json](https://github.com/samchon/typescript-json) and the JSON string
-     * conversion speed really be 2x faster.
+     * 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.
      */
-    json?: boolean;
+    contents: ISaleArticleComment.IContent[];
 
     /**
-     * Building `swagger.json` is also possible.
+     * Creation time.
      */
-    swagger?: IConfiguration.ISwagger;
+    created_at: string;
 }
-export namespace IConfiguration
+export namespace ISaleArticleComment
 {
     /**
-     * List of files or directories to include or exclude to specifying the NestJS 
-     * controllers.
+     * Store info.
      */
-    export interface IInput
+    export interface IStore
     {
         /**
-         * List of files or directories containing the NestJS controller classes.
+         * Body of the content.
          */
-        include: string[];
+        body: string;
 
         /**
-         * List of files or directories to be excluded.
+         * Whether to hide the writer name or not.
          */
-        exclude?: string[];
+        annonymous: boolean;
     }
 
     /**
-     * Building `swagger.json` is also possible.
+     * Content info.
      */
-    export interface ISwagger
+    export interface IContent
     {
         /**
-         * Output path of the `swagger.json`.
-         * 
-         * If you've configure only directory, the file name would be `swagger.json`. 
-         * Otherwise you configure file name and extension, the `swagger.json` file would
-         * be renamed to what you've configured.
+         * Primary Key.
          */
-        output: string;
-    }
-}
-```
-
-Instead of specifying `input` and `output` directories using the cli options, you can specify those directories as an independent configuration file. It's the `nestia.config.ts` and with the `nestia.config.ts` file, you also configure independent TypeScript compiler option from the `tsconfig.json`.
-
-Write below content as the `nestia.config.ts` file and place it onto the root directory of your backend project. After the configuration, you can generate the SDK only with the `npx nestia sdk` command, without any directory specification. 
+        id: string;
 
-```typescript
-import type nestia from "nestia";
+        /**
+         * Body of the content.
+         */
+        body: string;
 
-const config: nestia.IConfiguration = {
-    input: "src/controllers",
-    output: "src/api",
-    assert: false
-};
-export default config;
+        /**
+         * Creation time.
+         */
+        created_at: string;
+    }
+}
 ```
+</details>
 
-> Alternative options for the regular NestJS project:
-> 
-> ```typescript
-> export = {
->     input: "src/**/*.controller.ts",
->     /* input: {
->         include: ["src/controllers/**\/*.controller.ts"],
->         exclude: ["src/controllers/**\/fake_*.controller.ts"]
->     },*/
->     output: "src/api",
->     assert: true
-> }
-> ```
-
-
-
-### Recommended Structures
-When developing a NestJS backend server with this [nestia](https://github.com/samchon/nestia), I recommend you to follow below directory structure. The key princinple of below structure is to gathering all of the DTO interface structures into the `src/api/structures` directory and gather all of the controller classes into the `src/controllers` directory.
-
-If you place the SDK onto the `src/api` directory and gather all of the DTO interface structures into the `src/api/structures` directory, you can publish the SDK library very easily without any special configuration. Also when you're develop the test automation program, you can implement the API testing features very convenienty through the automatically generated SDK through this [nestia](https://github.com/samchon/nestia).
-
-  - src
-    - api
-      - **functional**: automatically generated SDK functions
-      - **structures**: DTO structures
-    - controllers
-    - providers
-    - models
-    - **test**: Test automation program using SDK functions
-  - package.json
-  - tsconfig.json
-  - nestia.config.ts
-
-For your deep understanding about this directory structure with this [nestia](https://github.com/samchon/nestia), I've prepared an example backend project. Looking around the example repository and reading the [README.md](https://github.com/samchon/backend#13-directories) of it, you can feel that such directory structure is how convenient for SDK publishing and test automation program implementation.
-
-  - https://github.com/samchon/backend
-
-
-
-
-## Demonstration
-To demonstrate which SDK codes would be generated by this [nestia](https://github.com/samchon/nestia):
-
-  - Representative files
-    - [DTO interface used in the RestAPI](https://github.com/samchon/nestia/tree/master/demo/simple/src/api/structures/ISaleArticleComment.ts)
-    - [Controllers of the NestJS](https://github.com/samchon/nestia/tree/master/demo/simple/src/controllers/ConsumerSaleArticleCommentsController.ts)
-    - [SDK generated by this **nestia**](https://github.com/samchon/nestia/tree/master/demo/simple/src/api/functional/consumers/sales/articles/comments/index.ts)
-    - [`swagger.json` generated by this **nestia**](https://github.com/samchon/nestia/tree/master/demo/simple/swagger.json)
-  - Demonstration Projects
-    - [encrypt](https://github.com/samchon/nestia/tree/master/demo/encrypt): Request and response body are fully encrypted
-    - [generic](https://github.com/samchon/nestia/tree/master/demo/generic): Generic typed controller classes
-    - [recursive](https://github.com/samchon/nestia/tree/master/demo/recursive): Recursive DTO interface, [swagger editor](https://editor.swagger.io) can't expresss it
-    - [simple](https://github.com/samchon/nestia/tree/master/demo/simple): Simple DTO interface and controller class
-    - [union](https://github.com/samchon/nestia/tree/master/demo/union): Only [nestia](https://github.com/samchon/nestia) can handle the union typed DTO interface
-
-### DTO
-Using pure interface type as DTO is possible.
-
-You dont' need to define any extra comment or decorator function to make the DTO (Data Transfer Object). Just define the DTO as a pure interface structure, then [nestia](https://github.com/samchon/nestia) will do everything instead of you. 
-
-If you're afraiding because your type is union or intersection, I can say that it does not matter. Even when generic or conditional type comes, it does not matter. Just enjoy the pure TypeScript type.
+<details>
+    <summary>
+        Generic typed DTO using <code>nestia</code>
+    </summary>
 
 ```typescript
 /**
- * Comment wrote on a sale related article.
+ * 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 ISaleComment
+export interface ISaleInquiry<Content extends ISaleInquiry.IContent> 
+    extends ISaleArticle<Content> 
 {
     /**
      * Primary Key.
      */
     id: number;
 
-    /**
-     * Type of the writer.
-     */
-    writer_type: "seller" | "consumer";
-
     /**
      * Name of the writer.
      */
-    writer_name: string;
+    writer: string;
 
     /**
-     * Contents of the comments.
+     * List of contents.
      * 
-     * 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
+     * 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: ISaleComment.IContent[];
+    contents: Content[];
 
     /**
      * Creation time.
      */
-    created_at: string;
+    createdAat: string;
+        
+    /**
+     * Formal answer from the seller.
+     */
+    answer: ISaleInquiryAnswer | null;
 }
-
-export namespace ISaleComment
+export namespace ISaleInquiry 
 {
     /**
-     * Store info.
+     * Content info.
      */
-    export interface IStore
+    export interface IContent 
     {
+        /**
+         * Primary Key
+         */
+        id: string;
+
+        /**
+         * Title of the content.
+         */
+        title: string;
+
         /**
          * Body of the content.
          */
         body: string;
-    }
 
-    /**
-     * Content info.
-     */
-    export interface IContent extends IStore
-    {
+        /**
+         * Attached files.
+         */
+        files: IAttachmentFile[];
+
         /**
          * Creation time.
          */
-        created_at: string;
+        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>
 
-### Controller
-If you've decided to adapt this [nestia](https://github.com/samchon/nestia) and you want to generate the SDK directly, you don't need any extra work. Just keep you controller class down and do noting. The only one exceptional case that you need an extra dedication is, when you want to explain about the API function to the client developers through the comments.
+
+
+
+### Advanced Controller Class
+Controller also can use the generic arguments.
+
+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 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 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
+    - abstract controller, [`SaleInquiriesController<Content, Store, Json>`](https://github.com/samchon/nestia/tree/master/demo/generic/src/controllers/SaleInquiriesController.ts)
+    - 1st sub-type controller, [`ConsumerSaleQuestionsController`](https://github.com/samchon/nestia/tree/master/demo/generic/src/controllers/ConsumerSaleQuestionsController.ts)
+    - 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
-@nest.Controller("consumers/:section/sales/:saleId/questions")
-export class ConsumerSaleQuestionsController
+import * as express from "express";
+import * as nest from "@nestjs/common";
+import helper from "nestia-helper";
+
+import { ISaleInquiry } from "@api/structures/ISaleInquiry";
+
+export abstract class SaleInquiriesController<
+        Content extends ISaleInquiry.IContent,
+        Store extends ISaleInquiry.IStore,
+        Json extends ISaleInquiry<Content>>
 {
     /**
-     * Store a new question.
+     * Constructor with type assert function.
+     */
+    protected constructor(private readonly assert: (input: Store) => void);
+
+    /**
+     * Store a new inquiry.
+     * 
+     * Write a new article inquirying about a sale.
      * 
      * @param request Instance of the Express.Request
      * @param section Code of the target section
      * @param saleId ID of the target sale
      * @param input Content to archive
+     * @return Newly archived inquiry
      * 
-     * @return Newly archived question
      * @throw 400 bad request error when type of the input data is not valid
      * @throw 401 unauthorized error when you've not logged in yet
      */
@@ -375,40 +476,101 @@ export class ConsumerSaleQuestionsController
     public store
         (
             @nest.Request() request: express.Request,
-            @nest.Param("section") section: string, 
-            @nest.Param("saleId") saleId: number, 
-            @nest.Body() input: ISaleQuestion.IStore
-        ): Promise<ISaleQuestion>;
+            @helper.TypedParam("section", "string") section: string, 
+            @helper.TypedParam("saleId", "string") saleId: string,
+            @nest.Body() input: Store
+        ): Promise<Json>;
+
+    /**
+     * Update an inquiry.
+     * 
+     * Update ordinary inquiry article. However, it would not modify the content reocrd
+     * {@link ISaleInquiry.IContent}, but be accumulated into the {@link ISaleInquiry.contents}. 
+     * Therefore, all of the poeple can read how the content has been changed.
+     * 
+     * @param request Instance of the Express.Request
+     * @param section Code of the target section
+     * @param saleId ID of the target sale
+     * @param id ID of the target article to be updated
+     * @param input New content to be overwritten
+     * @return The newly created content record
+     * 
+     * @throw 400 bad request error when type of the input data is not valid
+     * @throw 401 unauthorized error when you've not logged in yet
+     * @throw 403 forbidden error when the article is not yours
+     */
+    @nest.Put(":id")
+    public update
+        (
+            @nest.Request() request: express.Request,
+            @helper.TypedParam("section", "string") section: string, 
+            @helper.TypedParam("saleId", "string") saleId: string,
+            @helper.TypedParam("id", "number") id: number,
+            @nest.Body() input: Store
+        ): Promise<Json>;
 }
 ```
 
-### SDK
-When you run the [nestia](https://github.com/samchon/nestia) up using the upper controller class `ConsumerSaleQuestionsController`, the [nestia](https://github.com/samchon/nestia) would generate below function for the client developers, by analyzing the `ConsumerSaleQuestionsController` class in the compilation and runtime level.
 
-As you can see, the comments from the `ConsumerSaleQuestionsController.store()` are fully copied to the SDK function. Therefore, if you want to deliver detailed description about the API function, writing the detailed comment would be tne best choice.
+
+
+### Software Development Kit
+> `Swagger` is torturing client developers.
+>
+> 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 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 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 `nestia`, it is perfect.
+
+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 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)
+  - [generic/.../reviews/index.ts](https://github.com/samchon/nestia/tree/master/demo/generic/src/api/functional/consumers/sales/reviews/index.ts)
+  - [union/.../entire_articles/index.ts](https://github.com/samchon/nestia/tree/master/demo/union/src/api/functional/consumers/sales/entire_articles/index.ts)
 
 ```typescript
 /**
- * Store a new question.
+ * @packageDocumentation
+ * @module api.functional.consumers.sales.reviews
+ * @nestia Generated by Nestia - https://github.com/samchon/nestia 
+ */
+//================================================================
+import { Fetcher, Primitive } from "nestia-fetcher";
+import type { IConnection } from "nestia-fetcher";
+import { createStringifier } from "typescript-json";
+
+import type { ISaleReview } from "./../../../../structures/ISaleReview";
+import type { ISaleInquiry } from "./../../../../structures/ISaleInquiry";
+
+/**
+ * Store a new inquiry.
+ * 
+ * Write a new article inquirying about a sale.
  * 
  * @param connection connection Information of the remote HTTP(s) server with headers (+encryption password)
  * @param request Instance of the Express.Request
  * @param section Code of the target section
  * @param saleId ID of the target sale
  * @param input Content to archive
- * @return Newly archived question
+ * @return Newly archived inquiry
  * @throw 400 bad request error when type of the input data is not valid
  * @throw 401 unauthorized error when you've not logged in yet
  * 
+ * @controller ConsumerSaleReviewsController.store()
+ * @path POST /consumers/:section/sales/:saleId/reviews
  * @nestia Generated by Nestia - https://github.com/samchon/nestia
- * @controller ConsumerSaleQuestionsController.store()
- * @path POST /consumers/:section/sales/:saleId/questions/
  */
 export function store
     (
         connection: IConnection,
         section: string,
-        saleId: number,
+        saleId: string,
         input: Primitive<store.Input>
     ): Promise<store.Output>
 {
@@ -418,249 +580,304 @@ export function store
         store.ENCRYPTED,
         store.METHOD,
         store.path(section, saleId),
-        input
+        input,
+        store.stringify
     );
 }
 export namespace store
 {
-    export type Input = Primitive<ISaleInquiry.IStore>;
-    export type Output = Primitive<ISaleInquiry<ISaleArticle.IContent>>;
+    export type Input = Primitive<ISaleReview.IStore>;
+    export type Output = Primitive<ISaleInquiry<ISaleReview.IContent>>;
 
     export const METHOD = "POST" as const;
-    export const PATH: string = "/consumers/:section/sales/:saleId/questions";
+    export const PATH: string = "/consumers/:section/sales/:saleId/reviews";
     export const ENCRYPTED: Fetcher.IEncrypted = {
-        request: true,
-        response: true,
+        request: false,
+        response: false,
     };
 
-    export function path(section: string, saleId: number): string
+    export function path(section: string, saleId: string): string
     {
-        return `/consumers/${section}/sales/${saleId}/questions`;
+        return `/consumers/${section}/sales/${saleId}/reviews`;
     }
+    export const stringify = createStringifier<Input>();
 }
-```
 
-### `swagger.json`
-Even the `swagger.json` generation does not require any swagger comment and DTO decorator.
+/**
+ * Update an inquiry.
+ * 
+ * Update ordinary inquiry article. However, it would not modify the content reocrd
+ * {@link ISaleInquiry.IContent}, but be accumulated into the {@link ISaleInquiry.contents}. 
+ * Therefore, all of the poeple can read how the content has been changed.
+ * 
+ * @param connection connection Information of the remote HTTP(s) server with headers (+encryption password)
+ * @param request Instance of the Express.Request
+ * @param section Code of the target section
+ * @param saleId ID of the target sale
+ * @param id ID of the target article to be updated
+ * @param input New content to be overwritten
+ * @return The newly created content record
+ * @throw 400 bad request error when type of the input data is not valid
+ * @throw 401 unauthorized error when you've not logged in yet
+ * @throw 403 forbidden error when the article is not yours
+ * 
+ * @controller ConsumerSaleReviewsController.update()
+ * @path PUT /consumers/:section/sales/:saleId/reviews/:id
+ * @nestia Generated by Nestia - https://github.com/samchon/nestia
+ */
+export function update
+    (
+        connection: IConnection,
+        section: string,
+        saleId: string,
+        id: number,
+        input: Primitive<update.Input>
+    ): Promise<update.Output>
+{
+    return Fetcher.fetch
+    (
+        connection,
+        update.ENCRYPTED,
+        update.METHOD,
+        update.path(section, saleId, id),
+        input,
+        update.stringify
+    );
+}
+export namespace update
+{
+    export type Input = Primitive<ISaleReview.IStore>;
+    export type Output = Primitive<ISaleInquiry<ISaleReview.IContent>>;
 
-The [nestia](https://github.com/samchon/nestia) will generate the perfect `swagger.json` automatically, by analyzing your source code (DTO interface and controller class) in the compilation and runtime level. Furthermore, your descriptive comments would be automatically assigned into the adequate `description` property in the `swagger.json`.
+    export const METHOD = "PUT" as const;
+    export const PATH: string = "/consumers/:section/sales/:saleId/reviews/:id";
+    export const ENCRYPTED: Fetcher.IEncrypted = {
+        request: false,
+        response: false,
+    };
 
-```json
-{
-  "paths": {
-    "/consumers/{section}/sales/{saleId}/comments/{articleId}": {
-      "post": {
-        "tags": [],
-        "parameters": [
-          {
-            "name": "section",
-            "in": "path",
-            "description": "Code of the target section",
-            "schema": {
-              "type": "string",
-              "nullable": false
-            },
-            "required": true
-          },
-          {
-            "name": "saleId",
-            "in": "path",
-            "description": "ID of the target sale",
-            "schema": {
-              "type": "number",
-              "nullable": false
-            },
-            "required": true
-          },
-          {
-            "name": "articleId",
-            "in": "path",
-            "description": "ID of the target article",
-            "schema": {
-              "type": "number",
-              "nullable": false
-            },
-            "required": true
-          }
-        ],
-        "requestBody": {
-          "description": "Content to write",
-          "content": {
-            "application/json": {
-              "schema": {
-                "$ref": "#/components/schemas/ISaleComment.IStore"
-              }
-            }
-          },
-          "required": true
-        },
-        "responses": {
-          "201": {
-            "description": "Newly archived comment",
-            "content": {
-              "application/json": {
-                "schema": {
-                  "$ref": "#/components/schemas/ISaleComment"
-                }
-              }
-            }
-          },
-          "400": {
-            "description": "bad request error when type of the input data is not valid"
-          },
-          "401": {
-            "description": "unauthorized error when you've not logged in yet"
-          },
-          "403": {
-            "description": "forbidden error when you're a seller and the sale is not yours"
-          },
-          "404": {
-            "description": "not found error when unable to find the matched record"
-          }
-        },
-        "description": "Store a new comment."
-      }
-    }
-  },
-  "components": {
-    "schemas": {
-      "ISaleComment": {
-        "type": "object",
-        "properties": {
-          "id": {
-            "description": "Primary Key.",
-            "type": "number",
-            "nullable": false
-          },
-          "writer_type": {
-            "description": "Type of the writer.",
-            "type": "string",
-            "nullable": false
-          },
-          "writer_name": {
-            "description": "Name of the writer.",
-            "type": "string",
-            "nullable": false
-          },
-          "contents": {
-            "description": "Contents of the comments.\n\nWhen the comment writer tries to modify content, it would not modify the comment\ncontent but would be accumulated. Therefore, all of the people can read how\nthe content has been changed.",
-            "type": "array",
-            "items": {
-              "$ref": "#/components/schemas/ISaleComment.IContent"
-            },
-            "nullable": false
-          },
-          "created_at": {
-            "description": "Creation time.",
-            "type": "string",
-            "nullable": false
-          }
-        },
-        "nullable": false,
-        "required": [
-          "id",
-          "writer_type",
-          "writer_name",
-          "contents",
-          "created_at"
-        ],
-        "description": "Comment wrote on an article."
-      },
-      "ISaleComment.IContent": {
-        "type": "object",
-        "properties": {
-          "created_at": {
-            "description": "Creation time.",
-            "type": "string",
-            "nullable": false
-          },
-          "body": {
-            "description": "Body of the content.",
-            "type": "string",
-            "nullable": false
-          }
-        },
-        "nullable": false,
-        "required": [
-          "created_at",
-          "body"
-        ],
-        "description": "Content info."
-      },
-      "ISaleComment.IStore": {
-        "type": "object",
-        "properties": {
-          "body": {
-            "description": "Body of the content.",
-            "type": "string",
-            "nullable": false
-          }
-        },
-        "nullable": false,
-        "required": [
-          "body"
-        ],
-        "description": "Store info."
-      }
+    export function path(section: string, saleId: string, id: number): string
+    {
+        return `/consumers/${section}/sales/${saleId}/reviews/${id}`;
     }
-  }
+    export const stringify = createStringifier<Input>();
 }
 ```
 
 
 
 
+### Swagger
+Building `Swagger` is also possible and even much powerful.
 
-## Appendix
-### Template Project
-https://github.com/samchon/backend
+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.
 
-I support template backend project using this [nestia](https://github.com/samchon/nestia) library, [backend](https://github.com/samchon/backend).
+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.
 
-Reading the README content of the [backend](https://github.com/samchon/backend) template repository, you can find lots of example backend projects who've been generated from the [backend](https://github.com/samchon/backend). Furthermore, those example projects guide how to generate SDK library from the [nestia](https://github.com/samchon/nestia) and how to distribute the SDK library thorugh the NPM module.
+  - 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)
+    - [generic/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Fgeneric%2Fswagger.json)
+    - [union/swagger.json](https://editor.swagger.io/?url=https%3A%2F%2Fraw.githubusercontent.com%2Fsamchon%2Fnestia%2Fmaster%2Fdemo%2Funion%2Fswagger.json)
 
-Therefore, if you're planning to compose your own backend project using this [nestia](https://github.com/samchon/nestia), I recommend you to create the repository and learn from the [backend](https://github.com/samchon/backend) template project.
+![Swagger Editor](https://github.com/samchon/nestia/wiki/images/swagger-editor-comment.png)
 
-### Nestia-Helper
-https://github.com/samchon/nestia-helper
 
-Helper library of the `NestJS` with [nestia](https://github.com/samchon/nestia).
 
-[nestia-helper](https://github.com/samchon/nestia-helper) is a type of helper library for `Nestia` by enhancing decorator functions. Also, all of the decorator functions provided by this [nestia-helper](https://github.com/samchon/nestia-helper) are all fully compatible with the [nestia](https://github.com/samchon/nestia), who can generate SDK library by analyzing NestJS controller classes in the compilation level.
 
-Of course, this [nestia-helper](https://github.com/samchon/nestia-helper) is not essential for utilizing the `NestJS` and [nestia](https://github.com/samchon/nestia). You can generate SDK library of your NestJS developed backend server without this [nestia-helper](https://github.com/samchon/nestia-helper). However, as decorator functions of this [nestia-helper](https://github.com/samchon/nestia-helper) is enough strong, I recommend you to adapt this [nestia-helper](https://github.com/samchon/nestia-helper) when using `NestJS` and [nestia](https://github.com/samchon/nestia).
+## Configuration
+Components                   | `nestia.config.ts` | `CLI` | `@nestjs/swagger`
+-----------------------------|--------------------|-------|------------------
+Swagger Generation           | ✔  | ✔  | ✔
+SDK Generation               | ✔  | ✔  | ❌
+2x faster `JSON.stringify()` | ✔  | ❌ | ❌
+Type check in runtime        | ✔  | ❌ | ❌
+Custom compiler options      | ✔  | ❌ | ❌
 
-  - Supported decorator functions
-    - [EncryptedController](https://github.com/samchon/nestia-helper#encryptedcontroller), [EncryptedModule](https://github.com/samchon/nestia-helper#encryptedmodule)
-    - [TypedRoute](https://github.com/samchon/nestia-helper#typedroute), [EncryptedRoute](https://github.com/samchon/nestia-helper#encryptedroute)
-    - [TypedParam](https://github.com/samchon/nestia-helper#typedparam), [EncryptedBody](https://github.com/samchon/nestia-helper#encryptedbody), [PlainBody](https://github.com/samchon/nestia-helper#plainbody)
-    - [ExceptionManager](https://github.com/samchon/nestia-helper#exceptionmanager)
+`nestia` can configure generator options by two ways: CLI and configuration file.
 
-### Safe-TypeORM
-https://github.com/samchon/safe-typeorm
+At first, the CLI (Command Line Interface) is convenient, but does not support detailed options.
 
-[safe-typeorm](https://github.com/samchon/safe-typeorm) is another library that what I've developed, helping `TypeORM` in the compilation level and optimizes DB performance automatically without any extra dedication.
+```sh
+# BASIC COMMAND
+npx nestia <sdk|swagger> <source_directories_or_patterns> \
+    --exclude <exclude_directory_or_pattern> \
+    --out <output_directory_or_file>
+
+# EXAMPLES
+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 sdk
+npx nestia swagger
+```
+
+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
+/**
+ * Definition for the `nestia.config.ts` file.
+ * 
+ * @author Jeongho Nam - https://github.com/samchon
+ */
+export interface IConfiguration {
+    /**
+     * List of files or directories containing the `NestJS` controller classes.
+     */
+    input: string | string[] | IConfiguration.IInput;
+
+    /**
+     * Output directory that SDK would be placed in.
+     * 
+     * If not configured, you can't build the SDK library.
+     */
+    output?: string;
+
+    /**
+     * Compiler options for the TypeScript.
+     * 
+     * If you've omitted this property or the assigned property cannot fully cover the
+     * `tsconfig.json`, the properties from the `tsconfig.json` would be assigned to here.
+     * Otherwise, this property has been configured and it's detailed values are different 
+     * with the `tsconfig.json`, this property values would be overwritten.
+     * 
+     * ```typescript
+     * import ts from "typescript";
+     * 
+     * const tsconfig: ts.TsConfig;
+     * const nestiaConfig: IConfiguration;
+     * 
+     * const compilerOptions: ts.CompilerOptions = {
+     *     ...tsconfig.compilerOptions,
+     *     ...(nestiaConfig.compilerOptions || {})
+     * }
+     * ```
+     */
+    compilerOptions?: ts.CompilerOptions;
+
+    /**
+     * Whether to assert parameter types or not.
+     * 
+     * If you configure this property to be `true`, all of the function parameters would be
+     * checked through the [typescript-is](https://github.com/woutervh-/typescript-is). This
+     * option would make your SDK library slower, but would be much safer in the type level
+     * even in the runtime environment.
+     */
+    assert?: boolean;
+
+    /**
+     * Whether to optimize JSON string conversion 2x faster or not.
+     * 
+     * If you configure this property to be `true`, the SDK library would utilize the
+     * [typescript-json](https://github.com/samchon/typescript-json) and the JSON string
+     * conversion speed really be 2x faster.
+     */
+    json?: boolean;
+
+    /**
+     * Building `swagger.json` is also possible.
+     * 
+     * If not specified, you can't build the `swagger.json`.
+     */
+    swagger?: IConfiguration.ISwagger;
+}
+export namespace IConfiguration
+{
+    /**
+     * List of files or directories to include or exclude to specifying the `NestJS` 
+     * controllers.
+     */
+    export interface IInput {
+        /**
+         * List of files or directories containing the `NestJS` controller classes.
+         */
+        include: string[];
+
+        /**
+         * List of files or directories to be excluded.
+         */
+        exclude?: string[];
+    }
+
+    /**
+     * Building `swagger.json` is also possible.
+     */
+    export interface ISwagger {
+        /**
+         * Output path of the `swagger.json`.
+         * 
+         * If you've configured only directory, the file name would be the `swagger.json`. 
+         * Otherwise you've configured the full path with file name and extension, the 
+         * `swagger.json` file would be renamed to it.
+         */
+        output: string;
+    }
+}
+```
+</details>
+
+```typescript
+import type { IConfiguration } from "nestia";
+
+export const NESTIA_CONFIG: IConfiguration = {
+    input: "./src/controllers",
+    output: "./src/api",
+    json: true,
+    swagger: {
+        output: "./public/swagger.json"
+    }
+};
+export default NESTIA_CONFIG;
+```
+
+
+
+
+## Appendix
+### Dependencies of the SDK
+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.
+
+```bash
+# MOVE TO THE DISTRIBUTION DIRECTORY
+cd packages/api
+
+# INSTALL DEPENDENCIES OF THE SDK
+npx nestia install
+```
+
+### Template Repository
+https://github.com/samchon/backend
 
-Therefore, this [nestia](https://github.com/samchon/nestia) makes you to be much convenient in the API interaction level and safe-typeorm helps you to be much convenient in the DB interaction level. With those [nestia](https://github.com/samchon/nestia) and [safe-typeorm](https://github.com/samchon/safe-typeorm), let's implement the backend server much easily and conveniently.
+I support template backend project using this `nestia` library, `samchon/backend`.
 
-  - When writing [**SQL query**](https://github.com/samchon/safe-typeorm#safe-query-builder),
-    - Errors would be detected in the **compilation** level
-    - **Auto Completion** would be provided
-    - **Type Hint** would be supported
-  - You can implement [**App-join**](https://github.com/samchon/safe-typeorm#app-join-builder) very conveniently
-  - When [**SELECT**ing for **JSON** conversion](https://github.com/samchon/safe-typeorm#json-select-builder)
-    - [**App-Join**](https://github.com/samchon/safe-typeorm#app-join-builder) with the related entities would be automatically done
-    - Exact JSON **type** would be automatically **deduced**
-    - The **performance** would be **automatically tuned**
-  - When [**INSERT**](https://github.com/samchon/safe-typeorm#insert-collection)ing records
-    - Sequence of tables would be automatically sorted by analyzing dependencies
-    - The **performance** would be **automatically tuned**
+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.
 
-![Safe-TypeORM Demo](https://raw.githubusercontent.com/samchon/safe-typeorm/master/assets/demo/safe-query-builder.gif)
+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.
 
 ### Archidraw
 https://www.archisketch.com/
 
 I have special thanks to the Archidraw, where I'm working for.
 
-The Archidraw is a great IT company developing 3D interior editor and lots of solutions based on the 3D assets. Also, the Archidraw is the first company who had adopted this [nestia](https://github.com/samchon/nestia) on their commercial backend project, even this [nestia](https://github.com/samchon/nestia) was in the alpha level.
+The Archidraw is a great IT company developing 3D interior editor and lots of solutions based on the 3D assets. Also, the Archidraw is the first company who had adopted this nestia on their commercial backend project, even this nestia was in the alpha level.
+
+> 저희 회사 "아키드로우" 에서, 삼촌과 함께 일할 프론트 개발자 분들을, 최고의 대우로 모십니다.
+>
+> "아키드로우" 는 3D (인테리어) 에디터 및 이에 관한 파생 솔루션들을 만드는 회사입니다. 다만 저희 회사의 주력 제품이 3D 에디터라 하여, 반드시 3D 내지 랜더링에 능숙해야 하는 것은 아니니, 일반적인 프론트 개발자 분들도 망설임없이 지원해주십시오.
+>
+> 그리고 저희 회사는 분위기가 다들 친하고 즐겁게 지내는 분위기입니다. 더하여 위 `nestia` 나 [typescript-json](https://github.com/samchon/typescript-json) 및 [payments](https://github.com/archidraw/payments) 등, 제법 합리적(?)이고 재미난 프로젝트들을 다양하게 체험해보실 수 있습니다.
+>
+> - 회사소개서: [archidraw.pdf](https://github.com/archidraw/payments/files/7696710/archidraw.pdf)
+> - 기술 스택: React + TypeScript
+> - 이력서: 자유 양식
+> - 지원처: samchon@archisketch.com