nestia 2.1.0-dev.20220504 → 2.1.0

package/.github/ISSUE_TEMPLATE/BUG_REPORT.md

@@ -0,0 +1,42 @@
+---
+name: Bug report
+about: Create a report to help us improve
+
+---
+
+## Bug Report
+Note that, the bug you're reporting may have registered in the [issues](https://github.com/samchon/nestia/search?type=issues) by another user. Even the bug you're reporting may have been fixed in the `@next` version. In such reasons, I recommend you to check the old [issues](https://github.com/samchon/nestia/search?type=issues) and reproduct your code with the `@next` version before publishing the bug reporting issue.
+
+```bash
+`npm install --save-dev nestia@next`
+```
+
+When the same error occurs even in the `@next` version, then please fill the below template:
+
+### Summary
+Write a short summary of the bug in here.
+
+  - **SDK Version**: 2.1.0-dev.20220505
+  - **Expected behavior**: 
+  - **Actual behavior**: 
+
+Write detailed description in here.
+
+
+
+### Code occuring the bug
+```typescript
+/* Demonstration code occuring the bug you're reporting */
+```
+
+Write the demonstration code occuring the bug you're reporting.
+
+However, as the `nestia` is not a typical library who being used by the `import` statement but a executable program generating the SDK (Software Development Kit), it would be difficult to describe the bug with only the demonstration code.
+
+In that case, you'd better to make a demonstration project occuring the bug to report. After the demonstration repository composition, fill the below `bash` script section. Of course, if you can describe the bug clearly, without the demonstration project construction, just skip it. Creating the demonstration repository is not essential.
+
+```bash
+git clone https://github.com/someone/nestia-bug-report-xxx
+cd nestia-bug-report-xxx
+npx nestia sdk
+```

package/.github/ISSUE_TEMPLATE/FEATURE_REQUEST.md

@@ -0,0 +1,13 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+
+---
+
+## Feature Request
+Thanks for your suggestion. Feel free to just state your idea. Writing the issue, it would better to filling the below items:
+
+  - A description of the problem you're trying to solve.
+  - An overview of the suggested solution.
+  - Examples of how the suggestion whould work in various places.
+    - Code examples showing the expected behavior.

package/.github/ISSUE_TEMPLATE/QUESTION.md

@@ -0,0 +1,11 @@
+---
+name: Question
+about: What do you want to know?
+
+---
+
+## Question
+I always welcome any questions about this backend proejct. However, half of questions can be solved by traveling [README.md](https://github.com/samchon/nestia) or old [issues](https://github.com/samchon/nestia/search?type=issues). Therefore, I recommend you to visit them before. If you have a question that has not been treated and you're extremely urgently, just contact me.
+
+  - E-mail: samchon.github@gmail.com
+  - Mobile: 82-10-3627-0016

package/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+Before submitting a Pull Request, please test your code. 
+
+If you created a new created a new feature, then create the unit test function, too.
+
+```bash
+# COMPILE THE BACKEND SERVER
+npm run build
+
+# RUN THE TEST AUTOMATION PROGRAM
+npm run test
+```
+
+Learn more about the [CONTRIBUTING](CONTRIBUTING.md)

package/CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+[INSERT CONTACT METHOD].
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior,  harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+[https://www.contributor-covenant.org/version/2/0/code_of_conduct.html][v2.0].
+
+Community Impact Guidelines were inspired by 
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available 
+at [https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.0]: https://www.contributor-covenant.org/version/2/0/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

package/CONTRIBUTING.md

@@ -0,0 +1,72 @@
+# Contribution Guide
+## To Publish an issue
+Thanks for your advise. Before publishing an issue, please check some components.
+
+### 1. Search for duplicates
+Before publishing an issue, please check whether the duplicated issue exists or not.
+
+  - [Ordinary Issues](https://github.com/samchon/nestia/issues)
+
+### 2. Did you find a bug?
+When you reporting a bug, then please write about those items:
+
+  - What version you're using
+  - If possible, give me an isolated way to reproduce the behavior.
+  - The behavior your expect to see, and the actual behavior.
+
+### 3. Do you have a suggestion?
+I always welcome your suggestion. When you publishing a suggestion, then please write such items: 
+
+  - A description of the problem you're trying to solve.
+  - An overview of the suggested solution.
+  - Examples of how the suggestion whould work in various places.
+    - Code examples showing the expected behavior.
+
+
+
+
+## Contributing Code
+### Test your code
+Before sending a pull request, please test your new code. You type the command `npm run build &&& npm run test`, then compiling your code and test-automation will be all processed.
+
+```bash
+# COMPILE
+npm run build
+
+# DO TEST
+npm run test
+```
+
+If you succeeded to compile, but failed to pass the test-automation, then *debug* the test-automation module. I've configured the `.vscode/launch.json`. You just run the `VSCode` and click the `Start Debugging` button or press `F5` key. By the *debugging*, find the reason why the *test* is failed and fix it.
+
+### 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.
+
+Of course, if your contribution code does not require a test new project, don't mind this.
+
+
+
+
+## Sending a Pull Request
+Thanks for your contributing. Before sending a pull request to me, please check those components.
+
+### 1. Include enough descriptions
+When you send a pull request, please include a description, of what your change intends to do, on the content. Title, make it clear and simple such below:
+
+  - Refactor features
+  - Fix #17
+  - Add tests for #28
+
+### 2. Include adequate tests
+As I've mentioned in the `Contributing Code` section, your PR should pass the test-automation module. Your PR includes *new features* that have not being handled in the ordinary test-automation module, then also update *add the testing unit* please.
+
+If there're some specific reasons that could not pass the test-automation (not error but *intended*), then please update the ordinary test-automation module or write the reasons on your PR content and *const me update the test-automation module*.
+
+
+
+
+## References
+I've referenced contribution guidance of the TypeScript.
+  - https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md

package/README.md

@@ -1,5 +1,5 @@
 # Nestia
-Automatic SDK generator for the NestJS.
+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)
@@ -20,11 +20,17 @@ npx nestia sdk "src/**/*.controller.ts" --out "src/api"
 npx nestia swagger "src/controller" -- out "swagger.json"
 ```
 
-Don't write any `swagger` comment. Just deliver the SDK.
+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. You just run this **Nestia** up, then **Nestia** would generate the SDK automatically, by analyzing your controller classes in the compliation and runtime level.
+  - No swagger comment/decorator
+  - No DTO comment/decorator
+  - Only pure NestJS code is required
 
-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.
+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.
+
+> 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.
 
 ```typescript
 import api from "@samchon/bbs-api";
@@ -81,12 +87,28 @@ Just type the `nestia sdk <input> --out <output>` command in the console. When t
 
 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).
 
+### Swagger generation
+```bash
+npx nestia <source_controller_of_directory> --out <output_path>
+
+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 "./" 
+```
+
+The **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.
+
+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).
+
 ### Dependencies
 ```bash
 npx nestia install
 ```
 
-SDK library generated by the **Nestia** requires the [nestia-fetcher](https://github.com/samchon/nestia-fetcher) and [typescript-is](https://github.com/woutervh-/typescript-is) modules.
+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.
 
 The `npx nestia install` command installs those dependencies with `package.json` configuration.
 
@@ -94,8 +116,9 @@ The `npx nestia install` command installs those dependencies with `package.json`
 {
   "name": "payments-server-api",
   "dependencies": {
-    "nestia-fetcher": "^2.0.0",
-    "typescript-is": "^0.19.0"
+    "nestia-fetcher": "^2.0.1",
+    "typescript-is": "^0.19.0",
+    "typescript-json": "^2.0.9"
   }
 }
 ```
@@ -246,8 +269,8 @@ For your deep understanding about this directory structure with this **Nestia**,
 To demonstrate which SDK codes would be generated by this **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)
-    - [Structures used in the RestAPI](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/default/src/api/structures/sales/articles/ISaleArticle.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)
   - Demonstration Projects
     - [absolute](https://github.com/samchon/nestia/tree/master/src/test/demonstrations/absolute): Absolute path with the `baseUrl` option
@@ -260,6 +283,77 @@ To demonstrate which SDK codes would be generated by this **Nestia**:
     - [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`
 
+### DTO
+As you can see from the below code, the **Nestia** can use the interface directory.
+
+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. 
+
+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.
+ * 
+ * @author Jeongho Nam - https://github.com/samchon
+ */
+export interface ISaleComment
+{
+    /**
+     * Primary Key.
+     */
+    id: number;
+
+    /**
+     * Type of the writer.
+     */
+    writer_type: "seller" | "consumer";
+
+    /**
+     * Name of the writer.
+     */
+    writer_name: string;
+
+    /**
+     * 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: ISaleComment.IContent[];
+
+    /**
+     * Creation time.
+     */
+    created_at: string;
+}
+
+export namespace ISaleComment
+{
+    /**
+     * Store info.
+     */
+    export interface IStore
+    {
+        /**
+         * Body of the content.
+         */
+        body: string;
+    }
+
+    /**
+     * Content info.
+     */
+    export interface IContent extends IStore
+    {
+        /**
+         * Creation time.
+         */
+        created_at: string;
+    }
+}
+```
+
 ### 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.
 
@@ -348,6 +442,174 @@ 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`.
+
+```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."
+      }
+    }
+  }
+}
+```
+
+
 
 
 
@@ -357,7 +619,7 @@ https://github.com/samchon/backend
 
 I support template backend project using this **Nestia*** library, [backend](https://github.com/samchon/backend).
 
-Also, 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, the 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** 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.
 

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

package/lib/analyses/ControllerAnalyzer.js

@@ -134,7 +134,9 @@ var ControllerAnalyzer;
         // 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 imports = importDict.toJSON().map(function (pair) { return [pair.first, pair.second.toJSON()]; });
+        var imports = importDict
+            .toJSON()
+            .map(function (pair) { return [pair.first, pair.second.toJSON()]; });
         // CONFIGURE PATH
         var path = _Normalize_path(path_1.default.join(controller.path, func.path)
             .split("\\")

package/lib/factories/CommentFactory.d.ts

@@ -0,0 +1,5 @@
+import ts from "typescript";
+export declare namespace CommentFactory {
+    function generate(comments: ts.SymbolDisplayPart[]): string;
+}
+//# sourceMappingURL=CommentFactory.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"CommentFactory.d.ts","sourceRoot":"","sources":["../../src/factories/CommentFactory.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,MAAM,YAAY,CAAC;AAE5B,yBAAiB,cAAc,CAC/B;IACI,SAAgB,QAAQ,CAAC,QAAQ,EAAE,EAAE,CAAC,iBAAiB,EAAE,GAAG,MAAM,CAMjE;CACJ"}