Add Prettier and ESLint config files and format code for consistency.

Author: cnuahs

.prettierignore

@@ -0,0 +1,6 @@
+# build directories
+**/dist
+.angular
+
+# generated files
+src/schemas/*.validator.*

.vscode/settings.json

@@ -0,0 +1,9 @@
+{
+  "editor.defaultFormatter": "rvest.vs-code-prettier-eslint",
+  "editor.formatOnType": false, // required
+  "editor.formatOnPaste": true, // optional
+  "editor.formatOnSave": true, // optional
+  "editor.formatOnSaveMode": "file", // required to format on save
+  "files.autoSave": "onFocusChange", // optional but recommended
+  "vs-code-prettier-eslint.prettierLast": false // set as "true" to run 'prettier' last not first
+}

README.md

@@ -1,4 +1,6 @@
-# vhs-ext
+# semantic-history-search
+
+[![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
 
 A Chrome extension to provide semantic search over your browsing history. It goes beyond simple keyword matching of page titles, analysing the content of visited sites and allowing you to find previously visited pages based on their meaning and relevance to your queries. This provides intuitive rediscovery of previously visited sites or specific content from your history.
 

angular.json

@@ -3,7 +3,7 @@
   "version": 1,
   "newProjectRoot": "projects",
   "projects": {
-    "vhs-ext": {
+    "shs-ext": {
       "projectType": "application",
       "schematics": {},
       "root": "",
@@ -16,22 +16,18 @@
             "customWebpackConfig": {
               "path": "./custom-webpack.config.ts"
             },
-            "outputPath": "dist/vhs-ext",
+            "outputPath": "dist/shs-ext",
             "index": "src/index.html",
             "main": "src/main.ts",
-            "polyfills": [
-              "zone.js"
-            ],
+            "polyfills": ["zone.js"],
             "tsConfig": "tsconfig.app.json",
             "assets": [
               {
                 "glob": "**/*",
                 "input": "public"
               }
             ],
-            "styles": [
-              "src/styles.css"
-            ],
+            "styles": ["src/styles.css"],
             "scripts": []
           },
           "configurations": {
@@ -56,7 +52,7 @@
                   "inlineCritical": false
                 },
                 "fonts": false
-              },
+              }
             },
             "development": {
               "optimization": false,
@@ -70,10 +66,10 @@
           "builder": "@angular-devkit/build-angular:dev-server",
           "configurations": {
             "production": {
-              "buildTarget": "vhs-ext:build:production"
+              "buildTarget": "shs-ext:build:production"
             },
             "development": {
-              "buildTarget": "vhs-ext:build:development"
+              "buildTarget": "shs-ext:build:development"
             }
           },
           "defaultConfiguration": "development"
@@ -84,20 +80,15 @@
         "test": {
           "builder": "@angular-devkit/build-angular:karma",
           "options": {
-            "polyfills": [
-              "zone.js",
-              "zone.js/testing"
-            ],
+            "polyfills": ["zone.js", "zone.js/testing"],
             "tsConfig": "tsconfig.spec.json",
             "assets": [
               {
                 "glob": "**/*",
                 "input": "public"
               }
             ],
-            "styles": [
-              "src/styles.css"
-            ],
+            "styles": ["src/styles.css"],
             "scripts": []
           }
         }

custom-webpack.config.ts

@@ -1,34 +1,34 @@
 // see https://www.npmjs.com/package/@angular-builders/custom-webpack
-import type { Configuration } from 'webpack';
+import type { Configuration } from "webpack";
 
 // Note: AJV transforms/compiles a JSON Schema to an actual JS function. You can then call that function
 //       to validate input against said schema. BUT, to generate the function AJV uses dynamic code
 //       evaluation, which means doing this at runtime exposes us to the risk of code injection. To avoid
 //       this (and the need to add 'unsafe-eval' to our CSP in manifest.json) we use webpack's compile hook
 //       hook to "pre-compile" our validator function(s).
-import { compile } from './utils/ajv-utils';
+import { compile } from "./utils/ajv-utils";
 
 export default {
-    entry: { 
-        background: 'src/background.ts',
-        content: 'src/content.ts'
+  entry: {
+    background: "src/background.ts",
+    content: "src/content.ts",
+  },
+  plugins: [
+    {
+      apply: (compiler) => {
+        compiler.hooks.compile.tap("AjvPlugin", (_params) => {
+          compile({ schema: "src/schemas/settings.json", useDefaults: true });
+        });
+      },
     },
-    plugins: [
-        {
-            apply: (compiler) => {
-                compiler.hooks.compile.tap("AjvPlugin", (_params) => {
-                    compile( { schema: "src/schemas/settings.json", useDefaults: true } );
-                });
-            },
-        },
-    ],
-    optimization: {
-        runtimeChunk: false
-    },
-    node: {
-        global: true // Fix for "Uncaught ReferenceError: global is not defined" when importing Pinecone
-    },
-    experiments: {
-        topLevelAwait: true // Fix for "Module parse failed: The top-level-await experiment is not enabled" when instantiating PineconeStore
-    }
+  ],
+  optimization: {
+    runtimeChunk: false,
+  },
+  node: {
+    global: true, // Fix for "Uncaught ReferenceError: global is not defined" when importing Pinecone
+  },
+  experiments: {
+    topLevelAwait: true, // Fix for "Module parse failed: The top-level-await experiment is not enabled" when instantiating PineconeStore
+  },
 } as Configuration;