several fixes needed to run the script inside an angular project

Author: roguib

README.md

@@ -1,35 +1,34 @@
 # ng-vs-snippets
-![ts](https://badgen.net/badge/Built%20With/TypeScript/blue) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![made-for-VSCode](https://img.shields.io/badge/Made%20for-VSCode-1f425f.svg)](https://code.visualstudio.com/) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](http://makeapullrequest.com)
-
 
+![ts](https://badgen.net/badge/Built%20With/TypeScript/blue) [![License: MIT](https://img.shields.io/badge/License-MIT-yellow.svg)](https://opensource.org/licenses/MIT) [![made-for-VSCode](https://img.shields.io/badge/Made%20for-VSCode-1f425f.svg)](https://code.visualstudio.com/) [![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](http://makeapullrequest.com)
 
 Automatic VS Code snippet file generation for Angular codebases. Seamlessly maintain up-to-date VS Code snippets of all of your code.
 
 Currently, we support snippet generation from the following Angular elements:
 
 <center>
 
-| Element   | Status                                    |
-|-----------|:-----------------------------------------:|
-| Component | :white_check_mark: Supported              |
-| Directive | :construction_worker: Not yet supported   |
-| Pipe      | :construction_worker: Not yet supported   |
+| Element   |                 Status                  |
+| --------- | :-------------------------------------: |
+| Component |      :white_check_mark: Supported       |
+| Directive | :construction_worker: Not yet supported |
+| Pipe      | :construction_worker: Not yet supported |
 
 </center>
 
 ## Installation
 
-Install ```ng-vs-snippets``` as a dev-dependency in your Angular project. To do so, run:
+Install `ng-vs-snippets` as a dev-dependency in your Angular project. To do so, run:
 
 ```
 npm i @roguib/ng-vs-snippets --save-dev
 ```
 
-Create a ```package.json``` script to extract snippets from your codebase:
+Create a `package.json` script to extract snippets from your codebase:
 
 ```json
 "scripts": {
-    "ng-vs-snippets": "ng-vs-snippets --dir ./src --output ./.vscode",
+    "ng-vs-snippets": "ng-vs-snippets --dir . --output ./.vscode",
 },
 ```
 
@@ -39,21 +38,23 @@ Execute the script by running:
 npm run ng-vs-snippets
 ```
 
-The script will generate a ```out.code-snippets``` file containing all the definitions. **Make sure you don't have any file with the same name** since the data contained in that file **is going to be replaced**.
+The script will generate a `out.code-snippets` file containing all the definitions. **Make sure you don't have any file with the same name** since the data contained in that file **is going to be replaced**.
 
 ## Troubleshooting
-Sometimes, due to VS Code configuration issues, snippets don't appear in the suggestion's dropdown. Make sure to specify, in VS Code ```settings.json``` configuration file the following properties:
+
+Sometimes, due to VS Code configuration issues, snippets don't appear in the suggestion's dropdown. Make sure to specify, in VS Code `settings.json` configuration file the following properties:
 
 ```json
 "editor.tabCompletion": "on",
 "editor.snippetSuggestions": "top"
 ```
-If this doesn't fix the problem, open the command palette and search for ```Preferences: Configure User Snippets``` to ensure the editor is considering the fille where your generated snippets are defined.
+
+If this doesn't fix the problem, open the command palette and search for `Preferences: Configure User Snippets` to ensure the editor is considering the fille where your generated snippets are defined.
 
 ## Documentation
 
 You can find the [full document design at this url]().
 
 ## Contributing
 
-Pull requests are welcome :) Make sure to create an issue first so anyone's work is overlaped.
+Pull requests are welcome :) Make sure to create an issue first so anyone's work is overlaped.

package-lock.json

@@ -14,10 +14,10 @@
     "angular",
     "vs snippets"
   ],
-  "main": "build/ng-vs-snippets.js",
-  "types": "build/ng-vs-snippets.d.ts",
+  "main": "build/@roguib/ng-vs-snippets.js",
+  "types": "build/@roguib/ng-vs-snippets.d.ts",
   "bin": {
-    "ng-vs-snippets": "build/ng-vs-snippets.js"
+    "ng-vs-snippets": "build/@roguib/ng-vs-snippets.js"
   },
   "scripts": {
     "build:cjs": "rollup -c",

package.json

@@ -115,7 +115,6 @@ export const parser = (filePaths: Array<string>): Array<File> => {
     inputsData = file?.match(regularInputWithTypeSelector) || [];
     for (let input of inputsData) {
       let tmp: Array<string> = input.replace(/(\s+)/g, " ").split(" ");
-      logger.log("input data", inputsData);
       inputs.push({
         inputName: tmp[1].replace(":", ""),
         type: tmp[2].replace(";", ""),
@@ -263,8 +262,15 @@ export const parser = (filePaths: Array<string>): Array<File> => {
         extendedClassFilepath: extendedClassPath || undefined,
       });
     } else {
+      /**
+       * TODO: Instead of working with relative paths and converting them
+       * to absolute when needed, we can start the exec by transforming every
+       * relative path to absolute, and then clean up the resolve calls in the program
+       * that transforms the code into an spaguetti one. Also it could help by reducing
+       * the amount of times we call path.join(path.posix.resolve(), path);
+       */
       tmp.push({
-        fileLocation: filePath,
+        fileLocation: path.resolve(filePath),
         inputs: inputs,
         outputs: outputs,
         extendedClassFilepath: undefined,

src/parser.ts

@@ -21,8 +21,13 @@ export const resolve = (
    * @returns {string} The the path in the import expression
    */
   const extractPathFromImportExpr = (importExpr: string): string => {
-    let path = importExpr.substr(importExpr.indexOf('"') + 1);
-    return path.replace(/\"/g, "");
+    let pathIndex = importExpr.indexOf('"');
+
+    if (pathIndex === -1) {
+      pathIndex = importExpr.indexOf("'");
+    }
+    let path = importExpr.substr(pathIndex + 1);
+    return path.replace(/\"/g, "").replace(/'/g, "");
   };
 
   let resolvedPath = "",
@@ -41,19 +46,24 @@ export const resolve = (
     }
 
     let compilerOptionsPathsKey = pathToFile.substr(0, pathToFile.indexOf("/")),
-      compilerOptionsPathsValue = "";
+      compilerOptionsPathsValue: Array<string> = [""];
     if (compilerOptionsPathsKey + "/*" in tsconfigFile?.compilerOptions.paths) {
       compilerOptionsPathsValue =
         tsconfigFile?.compilerOptions.paths[compilerOptionsPathsKey + "/*"];
     } // TODO: else throw an exception
 
+    compilerOptionsPathsValue[0] = compilerOptionsPathsValue[0].replace(
+      "/*",
+      ""
+    );
+
     // Notice that by calling path.join with a relative path of the base
     // path from ComponentClassPath and the full path of the file resolves into the
     // full path of the base path
     resolvedPath = path.join(
       path.posix.resolve(),
       pathToFile
-        .replace(compilerOptionsPathsKey, compilerOptionsPathsValue)
+        .replace(compilerOptionsPathsKey, compilerOptionsPathsValue[0])
         .replace(/(\s+)/g, " ")
         .replace(/"/g, "") + ".ts"
     );