Merge pull request #411 from tcet-opensource/development

BIWEEKLY MERGE

Author: TejasNair9977

.github/workflows/test.yml

@@ -10,6 +10,7 @@ on:
 env: 
   TOKEN_SECRET: ${{ secrets.TOKEN_SECRET }}
   DB_URL: ${{ secrets.DB_URL }}
+  ENVIRONMENT: ${{ secrets.ENVIRONMENT }}
 
 permissions:
     contents: read

.husky/pre-commit

@@ -0,0 +1,13 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+# npm test
+npx lint-staged
+
+if [ "$(uname)" == "Darwin" ]; then
+    npm run test
+elif [ "$(expr substr $(uname -s) 1 5)" == "Linux" ]; then
+    npm run test   
+elif [ "$(expr substr $(uname -s) 1 5)" == "MINGW" ]; then
+    npm run testWin
+fi

.lintstagedrc.json

@@ -0,0 +1,6 @@
+{
+  "*.js": [
+    "prettier --write",
+    "eslint --fix"
+  ]
+}

README.md

@@ -44,9 +44,9 @@ node -e "console.log(require('crypto').randomBytes(256).toString('base64'));
 You don't need to assign values to these parameters in double or single quotes, just write directly, .env automatically converts it into quoted string.   
 
 Once you are done with this, install the packages through `npm ci` which stands for clean install.
-Also, you need to run 'setup.js' file. You can do that by running following command in your terminal
+Also you need to run the following command to check for you eslint and jest testcases:
 ```
-node setup.js
+npm run prepare
 ```
 And finally, run the server with `npm run serverstart` or `npm run serverstartWin` depending on your operating system.
 

SECURITY.md

@@ -6,4 +6,4 @@ The project is still in its development phase, so plase report issues only if th
 
 ## Reporting a Vulnerability
 
-Please report (suspected) security vulnerabilities to **[me](mailto:[email protected])**. You will probably receive a response from me within 48 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity but historically within a few days.
+Please report (suspected) security vulnerabilities to **[me](mailto:[email protected])**. You will probably receive a response from me within 48 hours. If the issue is confirmed, we will release a patch as soon as possible depending on complexity but historically within a few days.