nestia 2.1.1 → 2.1.2-dev.20220509

package/CONTRIBUTING.md

@@ -42,7 +42,7 @@ If you succeeded to compile, but failed to pass the test-automation, then *debug
 ### Adding a Test
 As this `nestia` is not a typical library who being used by the `import` statement but a executable program generating the SDK (Software Development Kit), adding a test means that adding a demonstration project.
 
-I know that adding a demonstration project is much difficult than adding a test function, but there's no way if newly contributed code requires a new type of testing tool. Looking at the [src/test/demonstratios](src/test/demonstrations) directory and traveling the demonstration projects, create a new demonstration project following their structures and styles.
+I know that adding a demonstration project is much difficult than adding a test function, but there's no way if newly contributed code requires a new type of testing tool. Looking at the [src/test/demonstratios](demo) directory and traveling the demonstration projects, create a new demonstration project following their structures and styles.
 
 Of course, if your contribution code does not require a test new project, don't mind this.
 

package/README.md

@@ -20,7 +20,7 @@ npx nestia sdk "src/**/*.controller.ts" --out "src/api"
 npx nestia swagger "src/controller" -- out "swagger.json"
 ```
 
-Don't write any `swagger` comment and DTO decorator. Just run the **Nestia** up.
+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
@@ -28,7 +28,7 @@ Don't write any `swagger` comment and DTO decorator. Just run the **Nestia** up.
 
 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** up, then **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**, 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.
+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.
 
@@ -67,7 +67,7 @@ export async function test_article_read(connection: api.IConnection): Promise<vo
 npm install --save-dev nestia
 ```
 
-Installing the **Nestia** is very easy.
+Installing the [nestia](https://github.com/samchon/nestia) is very easy.
 
 Just type the `npm install --save-dev nestia` command in your NestJS backend project.
 
@@ -81,7 +81,7 @@ npx nestia sdk "src/controllers/consumers" "src/controllers/sellers" --out "src/
 npx nestia sdk "src/controllers" --exclude "src/**/Fake*.ts" --out "src/api"
 ```
 
-To generate a SDK library through the **Nestia** is very easy. 
+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.
 
@@ -97,7 +97,7 @@ npx nestia swagger "src/consumers" "src/sellers" --out "actors.json"
 npx nestia swagger "src/controllers" --exclude "src/**/Fake*.ts" -out "./" 
 ```
 
-The **Nestia** even supports the `swagger.json` generation and it's also extermely easy.
+The [nestia](https://github.com/samchon/nestia) even supports the `swagger.json` generation and it's also extermely easy.
 
 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.
 
@@ -108,7 +108,7 @@ Also, when generating a SDK using the cli options, `compilerOptions` would follo
 npx nestia install
 ```
 
-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](#nestiaconfigts) options.
+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.
 
 The `npx nestia install` command installs those dependencies with `package.json` configuration.
 
@@ -242,9 +242,9 @@ export default config;
 
 
 ### Recommended Structures
-When developing a NestJS backend server with this **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.
+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**.
+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
@@ -258,7 +258,7 @@ If you place the SDK onto the `src/api` directory and gather all of the DTO inte
   - tsconfig.json
   - nestia.config.ts
 
-For your deep understanding about this directory structure with this **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.
+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
 
@@ -266,33 +266,30 @@ For your deep understanding about this directory structure with this **Nestia**,
 
 
 ## Demonstration
-To demonstrate which SDK codes would be generated by this **Nestia**:
+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/src/test/demonstrations/default/src/api/structures/sales/articles/ISaleArticle.ts)
-    - [Controllers of the NestJS](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/default/src/controllers/base/SaleCommentsController.ts)
-    - [SDK generated by this **Nestia**](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/default/src/api/functional/consumers/sales/reviews/index.ts)
+    - [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)](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)](https://github.com/samchon/nestia/tree/master/demo/simple/swagger.json)
   - Demonstration Projects
-    - [absolute](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/absolute): Absolute path with the `baseUrl` option
-    - [alias@api](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/alias@api): The `src/api` directory has been aliased by `paths` option
-    - [alias@src](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/alias@src): Entire `src` directory has been aliased by `paths` option
-    - [default](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/default): No `tsconfig.json` and `nestia.config.ts`
-    - [esnext](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/esnext): ECMAScript target version is `ESNEXT`
-    - [exclude](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/exclude): Exclude option using the `--exclude` commad
-    - [nestia.config.ts](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/nestia.config.ts): Configured `nestia.config.ts` with `assert` mode
-    - [reference](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/reference): Configured input files as `src/**/*.controller.ts`
-    - [tsconfig.json](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/tsconfig.json): Special configuration through the `tsconfig.json`
+    - [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
-As you can see from the below code, the **Nestia** can use the interface directory.
+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** will do everything instead of you. 
+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.
 
 ```typescript
 /**
- * Comment wrote on an article.
+ * Comment wrote on a sale related article.
  * 
  * @author Jeongho Nam - https://github.com/samchon
  */
@@ -355,7 +352,7 @@ export namespace ISaleComment
 ```
 
 ### Controller
-If you've decided to adapt this **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.
+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.
 
 ```typescript
 @nest.Controller("consumers/:section/sales/:saleId/questions")
@@ -385,7 +382,7 @@ export class ConsumerSaleQuestionsController
 ```
 
 ### SDK
-When you run the **Nestia** up using the upper controller class `ConsumerSaleQuestionsController`, the **Nestia** would generate below function for the client developers, by analyzing the `ConsumerSaleQuestionsController` class in the compilation and runtime level.
+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.
 
@@ -445,7 +442,7 @@ export namespace store
 ### `swagger.json`
 Even the `swagger.json` generation does not require any swagger comment and DTO decorator.
 
-The **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`.
+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`.
 
 ```json
 {
@@ -617,20 +614,20 @@ The **Nestia** will generate the perfect `swagger.json` automatically, by analyz
 ### Template Project
 https://github.com/samchon/backend
 
-I support template backend project using this **Nestia*** library, [backend](https://github.com/samchon/backend).
+I support template backend project using this [nestia](https://github.com/samchon/nestia)* library, [backend](https://github.com/samchon/backend).
 
-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** and how to distribute the SDK library thorugh the NPM module.
+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.
 
-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 [backend](https://github.com/samchon/backend) template project.
+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.
 
 ### Nestia-Helper
 https://github.com/samchon/nestia-helper
 
-Helper library of the `NestJS` with **Nestia**.
+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**, who can generate SDK library by analyzing NestJS controller classes in the compilation level.
+[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**. 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**.
+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).
 
   - Supported decorator functions
     - [EncryptedController](https://github.com/samchon/nestia-helper#encryptedcontroller), [EncryptedModule](https://github.com/samchon/nestia-helper#encryptedmodule)
@@ -643,7 +640,7 @@ https://github.com/samchon/safe-typeorm
 
 [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.
 
-Therefore, this **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** and [safe-typeorm](https://github.com/samchon/safe-typeorm), let's implement the backend server much easily and conveniently.
+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.
 
   - When writing [**SQL query**](https://github.com/samchon/safe-typeorm#safe-query-builder),
     - Errors would be detected in the **compilation** level
@@ -658,11 +655,11 @@ Therefore, this **Nestia** makes you to be much convenient in the API interactio
     - Sequence of tables would be automatically sorted by analyzing dependencies
     - The **performance** would be **automatically tuned**
 
-![Safe-TypeORM Demo](https://raw.githubusercontent.com/samchon/safe-typeorm/master/assets/demonstrations/safe-query-builder.gif)
+![Safe-TypeORM Demo](https://raw.githubusercontent.com/samchon/safe-typeorm/master/assets/demo/safe-query-builder.gif)
 
 ### 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** on their commercial backend project, even this **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](https://github.com/samchon/nestia) on their commercial backend project, even this [nestia](https://github.com/samchon/nestia) was in the alpha level.

package/lib/IConfiguration.d.ts

@@ -11,31 +11,52 @@ export interface IConfiguration {
     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 omitted, the configuration would follow the `tsconfig.json`.
+     * 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 used instead.
+     *
+     * ```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 option to be `true`, all of the function parameters would be
-     * checked through the [typescript-is](https://github.com/woutervh-/typescript-is).
+     * 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 enahcne the type safety even in
+     * the runtime level.
      */
     assert?: boolean;
     /**
      * Whether to optimize JSON string conversion 2x faster or not.
      *
-     * If you configure this option to be `true`, the SDK library would utilize the
+     * 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;
 }
@@ -61,9 +82,9 @@ export declare namespace IConfiguration {
         /**
          * 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.
+         * 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;
     }

package/lib/IConfiguration.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"IConfiguration.d.ts","sourceRoot":"","sources":["../src/IConfiguration.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,YAAY,CAAC;AAE5B;;;;GAIG;AACH,MAAM,WAAW,cAAc;IAE3B;;OAEG;IACH,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,cAAc,CAAC,MAAM,CAAC;IAEjD;;OAEG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAEhB;;;;OAIG;IACH,eAAe,CAAC,EAAE,EAAE,CAAC,eAAe,CAAC;IAErC;;;;;OAKG;IACH,MAAM,CAAC,EAAE,OAAO,CAAC;IAEjB;;;;;;OAMG;IACH,IAAI,CAAC,EAAE,OAAO,CAAC;IAEf;;OAEG;IACH,OAAO,CAAC,EAAE,cAAc,CAAC,QAAQ,CAAC;CACrC;AACD,yBAAiB,cAAc,CAC/B;IACI;;;OAGG;IACH,UAAiB,MAAM;QAEnB;;WAEG;QACH,OAAO,EAAE,MAAM,EAAE,CAAC;QAElB;;WAEG;QACH,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;KACtB;IAED;;OAEG;IACH,UAAiB,QAAQ;QAErB;;;;;;WAMG;QACH,MAAM,EAAE,MAAM,CAAC;KAClB;CACJ"}
+{"version":3,"file":"IConfiguration.d.ts","sourceRoot":"","sources":["../src/IConfiguration.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,YAAY,CAAC;AAE5B;;;;GAIG;AACH,MAAM,WAAW,cAAc;IAE3B;;OAEG;IACH,KAAK,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,cAAc,CAAC,MAAM,CAAC;IAEjD;;;;OAIG;IACH,MAAM,CAAC,EAAE,MAAM,CAAC;IAEhB;;;;;;;;;;;;;;;;;;;OAmBG;IACH,eAAe,CAAC,EAAE,EAAE,CAAC,eAAe,CAAC;IAErC;;;;;;;OAOG;IACH,MAAM,CAAC,EAAE,OAAO,CAAC;IAEjB;;;;;;OAMG;IACH,IAAI,CAAC,EAAE,OAAO,CAAC;IAEf;;;;OAIG;IACH,OAAO,CAAC,EAAE,cAAc,CAAC,QAAQ,CAAC;CACrC;AACD,yBAAiB,cAAc,CAC/B;IACI;;;OAGG;IACH,UAAiB,MAAM;QAEnB;;WAEG;QACH,OAAO,EAAE,MAAM,EAAE,CAAC;QAElB;;WAEG;QACH,OAAO,CAAC,EAAE,MAAM,EAAE,CAAC;KACtB;IAED;;OAEG;IACH,UAAiB,QAAQ;QAErB;;;;;;WAMG;QACH,MAAM,EAAE,MAAM,CAAC;KAClB;CACJ"}

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;CA2IJ"}
+{"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"}

package/lib/analyses/ControllerAnalyzer.js

@@ -76,47 +76,36 @@ var ControllerAnalyzer;
         CLASS
     --------------------------------------------------------- */
     function _Analyze_controller(checker, controller, classNode) {
-        var e_1, _a, e_2, _b;
-        var ret = [];
+        var e_1, _a;
         var classType = checker.getTypeAtLocation(classNode);
         var genericDict = GenericAnalyzer_1.GenericAnalyzer.analyze(checker, classNode);
+        var ret = [];
+        var _loop_1 = function (property) {
+            // GET METHOD DECLARATION
+            var declaration = (property.declarations || [])[0];
+            if (!declaration || !typescript_1.default.isMethodDeclaration(declaration))
+                return "continue";
+            // IDENTIFIER MUST BE
+            var identifier = declaration.name;
+            if (!typescript_1.default.isIdentifier(identifier))
+                return "continue";
+            // ANALYZED WITH THE REFLECTED-FUNCTION
+            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);
+        };
         try {
-            for (var _c = __values(classType.getProperties()), _d = _c.next(); !_d.done; _d = _c.next()) {
-                var property = _d.value;
-                if (property.declarations) {
-                    var _loop_1 = function (declaration) {
-                        // TARGET ONLY METHOD
-                        if (!typescript_1.default.isMethodDeclaration(declaration))
-                            return "continue";
-                        // IT MUST BE
-                        var identifier = declaration.name;
-                        if (!typescript_1.default.isIdentifier(identifier))
-                            return "continue";
-                        // ANALYZED WITH THE REFLECTED-FUNCTION
-                        var func = controller.functions.find(function (f) { return f.name === identifier.escapedText; });
-                        if (func !== undefined)
-                            ret.push(_Analyze_function(checker, controller, genericDict, func, declaration));
-                    };
-                    try {
-                        for (var _e = (e_2 = void 0, __values(property.declarations)), _f = _e.next(); !_f.done; _f = _e.next()) {
-                            var declaration = _f.value;
-                            _loop_1(declaration);
-                        }
-                    }
-                    catch (e_2_1) { e_2 = { error: e_2_1 }; }
-                    finally {
-                        try {
-                            if (_f && !_f.done && (_b = _e.return)) _b.call(_e);
-                        }
-                        finally { if (e_2) throw e_2.error; }
-                    }
-                }
+            for (var _b = __values(classType.getProperties()), _c = _b.next(); !_c.done; _c = _b.next()) {
+                var property = _c.value;
+                _loop_1(property);
             }
         }
         catch (e_1_1) { e_1 = { error: e_1_1 }; }
         finally {
             try {
-                if (_d && !_d.done && (_a = _c.return)) _a.call(_c);
+                if (_c && !_c.done && (_a = _b.return)) _a.call(_b);
             }
             finally { if (e_1) throw e_1.error; }
         }
@@ -125,15 +114,16 @@ var ControllerAnalyzer;
     /* ---------------------------------------------------------
         FUNCTION
     --------------------------------------------------------- */
-    function _Analyze_function(checker, controller, genericDict, func, declaration) {
+    function _Analyze_function(checker, controller, genericDict, func, symbol) {
         // PREPARE ASSETS
-        var signature = checker.getSignatureFromDeclaration(declaration);
+        var type = checker.getTypeOfSymbolAtLocation(symbol, symbol.valueDeclaration);
+        var signature = checker.getSignaturesOfType(type, typescript_1.default.SignatureKind.Call)[0];
         if (signature === undefined)
-            throw new Error("Error on ControllerAnalyzer._Analyze_function(): unable to get the ignature from the ".concat(controller.name, ".").concat(func.name, "()."));
+            throw new Error("Error on ControllerAnalyzer._Analyze_function(): unable to get the signature from the ".concat(controller.name, ".").concat(func.name, "()."));
         var importDict = new HashMap_1.HashMap();
         // EXPLORE CHILDREN TYPES
-        var parameters = func.parameters.map(function (param) { return _Analyze_parameter(checker, genericDict, importDict, controller, func.name, param, declaration.parameters[param.index]); });
-        var output = ImportAnalyzer_1.ImportAnalyzer.analyze(checker, genericDict, importDict, checker.getReturnTypeOfSignature(signature));
+        var parameters = func.parameters.map(function (param) { return _Analyze_parameter(checker, genericDict, importDict, controller, func.name, param, signature.getParameters()[param.index]); });
+        var output = ImportAnalyzer_1.ImportAnalyzer.analyze(checker, genericDict, importDict, signature.getReturnType());
         var imports = importDict
             .toJSON()
             .map(function (pair) { return [pair.first, pair.second.toJSON()]; });
@@ -154,9 +144,8 @@ var ControllerAnalyzer;
     /* ---------------------------------------------------------
         PARAMETER
     --------------------------------------------------------- */
-    function _Analyze_parameter(checker, genericDict, importDict, controller, funcName, param, declaration) {
-        var symbol = checker.getSymbolAtLocation(declaration.name);
-        var type = checker.getTypeOfSymbolAtLocation(symbol, declaration);
+    function _Analyze_parameter(checker, genericDict, importDict, controller, funcName, param, symbol) {
+        var type = checker.getTypeOfSymbolAtLocation(symbol, symbol.valueDeclaration);
         var name = symbol.getEscapedName().toString();
         // VALIDATE PARAMETERS
         if ((param.category === "query" || param.category === "body") && param.field !== undefined)

package/lib/factories/MetadataFactory.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"MetadataFactory.d.ts","sourceRoot":"","sources":["../../src/factories/MetadataFactory.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,YAAY,CAAC;AAG5B,OAAO,EAAE,SAAS,EAAE,MAAM,yBAAyB,CAAC;AAGpD,OAAO,EAAE,kBAAkB,EAAE,MAAM,sBAAsB,CAAC;AAG1D,yBAAiB,eAAe,CAChC;IACI,MAAM,QAAQ,UAAU,GAAG,kBAAkB,CAAC;IAE9C,SAAgB,QAAQ,CAEhB,OAAO,EAAE,EAAE,CAAC,WAAW,EACvB,IAAI,EAAE,EAAE,CAAC,IAAI,GAAG,IAAI,EACpB,UAAU,GAAE,UAAiC,GAC9C,SAAS,CAAC,YAAY,GAAG,IAAI,CAenC;CA6NJ"}
+{"version":3,"file":"MetadataFactory.d.ts","sourceRoot":"","sources":["../../src/factories/MetadataFactory.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,MAAM,YAAY,CAAC;AAG5B,OAAO,EAAE,SAAS,EAAE,MAAM,yBAAyB,CAAC;AACpD,OAAO,EAAE,kBAAkB,EAAE,MAAM,sBAAsB,CAAC;AAG1D,yBAAiB,eAAe,CAChC;IACI,MAAM,QAAQ,UAAU,GAAG,kBAAkB,CAAC;IAE9C,SAAgB,QAAQ,CAEhB,OAAO,EAAE,EAAE,CAAC,WAAW,EACvB,IAAI,EAAE,EAAE,CAAC,IAAI,GAAG,IAAI,EACpB,UAAU,GAAE,UAAiC,GAC9C,SAAS,CAAC,YAAY,GAAG,IAAI,CAenC;CA0NJ"}

package/lib/factories/MetadataFactory.js

@@ -43,7 +43,6 @@ exports.MetadataFactory = void 0;
 var crypto_1 = __importDefault(require("crypto"));
 var typescript_1 = __importDefault(require("typescript"));
 var Singleton_1 = require("tstl/thread/Singleton");
-var CommentFactory_1 = require("./CommentFactory");
 var MetadataCollection_1 = require("./MetadataCollection");
 var TypeFactry_1 = require("./TypeFactry");
 var MetadataFactory;
@@ -208,11 +207,8 @@ var MetadataFactory;
                 var type = checker.getTypeOfSymbolAtLocation(prop, node);
                 // CHILD METADATA BY ADDITIONAL EXPLORATION
                 var child = explore(collection, checker, type);
-                if (child) {
-                    if (node.questionToken)
-                        child.required = false;
-                    child.description = CommentFactory_1.CommentFactory.generate(prop.getDocumentationComment(checker));
-                }
+                if (child && node.questionToken)
+                    child.required = false;
                 object.properties[key] = child;
             }
         }

package/lib/factories/TypeFactry.js

@@ -43,7 +43,7 @@ var TypeFactory;
     }
     function full_name(checker, type) {
         // PRIMITIVE
-        var symbol = type.getSymbol() || type.aliasSymbol;
+        var symbol = type.aliasSymbol || type.getSymbol();
         if (symbol === undefined)
             return checker.typeToString(type, undefined, undefined);
         // UNION OR INTERSECT

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nestia",
-  "version": "2.1.1",
+  "version": "2.1.2-dev.20220509",
   "description": "Automatic SDK and Document generator for the NestJS",
   "main": "lib/index.js",
   "typings": "lib/index.d.ts",