Upgrade to hoveboard latest version 2022 (Sept)

.eslintrc.json

@@ -1,56 +1,61 @@
 {
+  "root": true,
   "extends": [
     "eslint:recommended",
-    "google",
-    "plugin:polymer/polymer-2"
+    "plugin:jest/all",
+    "plugin:testing-library/dom",
+    "plugin:jest-dom/recommended",
+    "plugin:import/errors",
+    "plugin:import/typescript",
+    "prettier"
   ],
+  "parser": "@typescript-eslint/parser",
   "parserOptions": {
-    "ecmaVersion": 6
+    "sourceType": "module",
+    "ecmaVersion": 2020
   },
   "env": {
     "browser": true,
     "es6": true
   },
-  "plugins": [
-    "html",
-    "polymer"
-  ],
+  "plugins": ["jest", "@typescript-eslint", "html", "import"],
+  "ignorePatterns": ["dist/"],
+  "settings": {
+    "import/parsers": {
+      "@typescript-eslint/parser": [".ts", ".tsx"]
+    },
+    "import/resolver": {
+      "typescript": {
+        "alwaysTryTypes": true,
+        "project": "./tsconfig.json"
+      }
+    }
+  },
   "rules": {
     "brace-style": "off",
     "new-cap": "off",
-    "no-var": "off",
+    "no-var": "error",
     "require-jsdoc": "off",
-    "max-len": ["error", { "code": 100 }],
+    "max-len": ["error", { "code": 120 }],
     "object-curly-spacing": ["error", "always"],
-    "space-before-function-paren": ["error", {"anonymous": "always", "named": "never", "asyncArrow": "always"}],
-    "linebreak-style": 0
+    "space-before-function-paren": [
+      "error",
+      { "anonymous": "always", "named": "never", "asyncArrow": "always" }
+    ],
+    "linebreak-style": 0,
+    "jest/no-hooks": "off",
+    "jest/prefer-expect-assertions": "off",
+    "jest/require-hook": "off"
   },
+  "overrides": [
+    {
+      "files": ["*.ts", "*.tsx"],
+      "rules": {
+        "@typescript-eslint/no-unused-vars": ["error", { "args": "none" }]
+      }
+    }
+  ],
   "globals": {
-    "Polymer": true,
-    "firebase": true,
-    "google": true,
-    "ga": true,
-    "ShadyCSS": true,
-    "ReduxMixin": true,
-    "uiActions": true,
-    "routingActions": true,
-    "dialogsActions": true,
-    "toastActions": true,
-    "ticketsActions": true,
-    "partnersActions": true,
-    "videosActions": true,
-    "blogActions": true,
-    "speakersActions": true,
-    "previousSpeakersActions": true,
-    "sessionsActions": true,
-    "scheduleActions": true,
-    "galleryActions": true,
-    "teamActions": true,
-    "userActions": true,
-    "subscribeActions": true,
-    "notificationsActions": true,
-    "helperActions": true,
-    "DIALOGS": true,
-    "NOTIFICATIONS_STATUS": true
+    "ServiceWorkerGlobalScope": true
   }
 }

CODE_OF_CONDUCT.md → .github/CODE_OF_CONDUCT.md

@@ -8,19 +8,19 @@ In the interest of fostering an open and welcoming environment, we as contributo
 
 Examples of behavior that contributes to creating a positive environment include:
 
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
+- Using welcoming and inclusive language
+- Being respectful of differing viewpoints and experiences
+- Gracefully accepting constructive criticism
+- Focusing on what is best for the community
+- Showing empathy towards other community members
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a professional setting
+- The use of sexualized language or imagery and unwelcome sexual attention or advances
+- Trolling, insulting/derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or electronic address, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ## Our Responsibilities
 
@@ -34,7 +34,7 @@ This Code of Conduct applies both within project spaces and in public spaces whe
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality about the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
 Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 

CONTRIBUTING.md → .github/CONTRIBUTING.md

@@ -6,62 +6,58 @@ Hoverboard are built in the open, and the GDG[x] team eagerly encourage any and
 
 **If you are filing an issue to request a feature**, please provide a clear description of the feature. It can be helpful to describe answers to the following questions:
 
- 1. **Who will use the feature?** _“As someone filling out a form…”_
- 2. **When will they use the feature?** _“When I enter an invalid value…”_
- 3. **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
+1.  **Who will use the feature?** _“As someone filling out a form…”_
+2.  **When will they use the feature?** _“When I enter an invalid value…”_
+3.  **What is the user’s goal?** _“I want to be visually notified that the value needs to be corrected…”_
 
 **If you are filing an issue to report a bug**, please provide:
 
- 1. **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
+1.  **A clear description of the bug and related expectations.** Consider using the following example template for reporting a bug:
 
- ```markdown
-
- The `paper-foo` element causes the page to turn pink when clicked.
+```markdown
+The `paper-foo` element causes the page to turn pink when clicked.
 
- ## Expected outcome
+## Expected outcome
 
- The page stays the same color.
+The page stays the same color.
 
- ## Actual outcome
+## Actual outcome
 
- The page turns pink.
+The page turns pink.
 
- ## Steps to reproduce
+## Steps to reproduce
 
- 1. Put a `paper-foo` element in the page.
- 2. Open the page in a web browser.
- 3. Click the `paper-foo` element.
-
- ```
+1. Put a `paper-foo` element in the page.
+2. Open the page in a web browser.
+3. Click the `paper-foo` element.
+```
 
- 3. **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
+3.  **A list of browsers where the problem occurs.** This can be skipped if the problem is the same across all browsers.
 
 ### Submitting Pull Requests
 
 **Before creating a pull request**, please ensure that an issue exists for the corresponding change in the pull request that you intend to make. **If an issue does not exist, please create one per the guidelines above**. The goal is to discuss the design and necessity of the proposed change with Polymer authors and community before diving into a pull request.
 
 When submitting pull requests, please provide:
 
- 1. **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
+1.  **A reference to the corresponding issue** or issues that will be closed by the pull request. Please refer to these issues in the pull request description using the following syntax:
 
- ```markdown
- (For a single issue)
- Fixes #20
+```markdown
+(For a single issue)
+Fixes #20
 
- (For multiple issues)
- Fixes #32, fixes #40
- ```
+(For multiple issues)
+Fixes #32, fixes #40
+```
 
- 2. **A succinct description of the design** used to fix any related issues. For example:
+2.  **A succinct description of the design** used to fix any related issues. For example:
 
- ```markdown
- This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
- ```
+```markdown
+This fixes #20 by removing styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
+```
 
- 3. **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
+3.  **At least one test for each bug fixed or feature added** as part of the pull request. Pull requests that fix bugs or add features without accompanying tests will not be considered.
 
 If a proposed change contains multiple commits, please [squash commits](https://www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash-commits-in-a-github-pull-request) to as few as is necessary to succinctly express the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
 
-
-
-_Copied from [Polymer Elements contributing guide](https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md)_
+_Copied from [Polymer Elements contributing guide](https://github.com/PolymerElements/ContributionGuide)_

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,40 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,19 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: enhancement, discussion
+assignees: ''
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/dependabot.yml

@@ -0,0 +1,15 @@
+version: 2
+updates:
+  - package-ecosystem: github-actions
+    directory: '/'
+    schedule:
+      interval: monthly
+  - package-ecosystem: npm
+    directory: '/'
+    schedule:
+      interval: monthly
+    open-pull-requests-limit: 25
+  - package-ecosystem: npm
+    directory: '/functions'
+    schedule:
+      interval: monthly

.github/workflows/deploy-preview.yaml

@@ -0,0 +1,20 @@
+name: Deploy Preview
+on: pull_request
+jobs:
+  build_and_preview:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - name: Create temp serviceAccount.json
+        run: echo "{}" > serviceAccount.json
+      - run: npm ci
+      - run: npm run build
+      - uses: FirebaseExtended/action-hosting-deploy@v0
+        with:
+          repoToken: '${{ secrets.GITHUB_TOKEN }}'
+          # See docs/tutorials/04-deploy.md for configuring these
+          projectId: hoverboard-master
+          firebaseServiceAccount: '${{ secrets.FIREBASE_SERVICE_ACCOUNT_HOVERBOARD_MASTER }}'

.github/workflows/deploy.yaml

@@ -0,0 +1,24 @@
+name: Deploy
+on:
+  push:
+    branches:
+      - main
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-node@v3
+        with:
+          node-version: 16
+      - name: Create temp serviceAccount.json
+        run: echo "{}" > serviceAccount.json
+      - run: npm ci
+      - run: npm run build
+      - uses: w9jds/[email protected]
+        with:
+          args: deploy
+        env:
+          # See docs/tutorials/04-deploy.md for configuring these
+          PROJECT_ID: hoverboard-master
+          GCP_SA_KEY: ${{ secrets.FIREBASE_SERVICE_ACCOUNT_HOVERBOARD_MASTER }}