Matej/pushed updates (#8)

Author: Meemaw

.eslintignore

@@ -1,2 +1,2 @@
 node_modules
-lib
+dist

.eslintrc

@@ -0,0 +1,18 @@
+module.exports = {
+  env: {
+    browser: true,
+    node: true
+  },
+  root: true,
+  reportUnusedDisableDirectives: true,
+  parser: '@typescript-eslint/parser',
+  plugins: ['@typescript-eslint', 'prettier'],
+  extends: [
+    'eslint:recommended',
+    'plugin:@typescript-eslint/recommended',
+    'plugin:prettier/recommended'
+  ],
+  rules: {
+    'prettier/prettier': 2
+  }
+};

.eslintrc.js

@@ -1,27 +1,33 @@
 ## Change Overview
+
 <!-- Describe the change clearly and succinctly, why it is needed, and what the result of the change will do -->
 
 ## Impact of Change
+
 <!-- Check all that apply and add other impacts that might not be listed -->
 
 - [ ] Bug fix
-    - [ ] External Facing (resolves an issue customers are currently experiencing)
-    - [ ] Security Impact (fixes a potential vulnerability)
+  - [ ] External Facing (resolves an issue customers are currently experiencing)
+  - [ ] Security Impact (fixes a potential vulnerability)
 - [ ] Feature
-    - [ ] Visible Change (changes semver of API surface or other change that would impact user/dev experience)
-    - [ ] High Usage (impacts a major part of the core workflow for users)
+  - [ ] Visible Change (changes semver of API surface or other change that would impact user/dev experience)
+  - [ ] High Usage (impacts a major part of the core workflow for users)
 - [ ] Performance Improvement
 - [ ] Refactoring
-- [ ] Other: *Describe here*
+- [ ] Other: _Describe here_
 
 ## Detailed Technical Description of Change
+
 <!-- Detail the technical approach and rationale for the change that you are working on. Are there are known limitations to the implementation or usage? -->
 
 ## Testing Approach and Results
+
 <!-- Outline how you will test the change, provide rationale for whether unit / dev / system tests are needed (or why not), and post the evidence of your testing -->
 
 ## Collateral Work or Changes
+
 <!-- Provide analysis of the overall impacts caused by your change. Does another system need to be updated to support the change? Does a configuration file need to be updated? etc -->
 
 ## Operational Impact
-<!-- Are new metrics available with this change? Are they being logged? Do new dashboards or operational alerts need to be setup? -->
+
+<!-- Are new metrics available with this change? Are they being logged? Do new dashboards or operational alerts need to be setup? -->

.github/pull_request_template.md

@@ -0,0 +1,52 @@
+---
+name: code-quality
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+
+env:
+  CI: true
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16.11.0'
+
+      - name: Install dependencies
+        run: npm ci
+      - name: Run linters
+        run: npm run lint:check
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16.11.0'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Run tests
+        run: npm run test -- --coverage --ci --runInBand
+
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - uses: actions/setup-node@v2
+        with:
+          node-version: '16.11.0'
+
+      - name: Install dependencies
+        run: npm ci
+
+      - name: Build
+        run: npm run build

.github/workflows/ci.yml

@@ -1,5 +1,5 @@
 node_modules
-
+dist
 coverage
 
 # Logs
@@ -18,4 +18,4 @@ yarn-error.log*
 # Yarn Integrity file
 .yarn-integrity
 
-.nyc_output
+

.gitignore

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+yarn lint-staged

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/bin/sh
+. "$(dirname "$0")/_/husky.sh"
+
+yarn check-types