.gitea/workflows/demo.yaml

@@ -0,0 +1,23 @@
+name: E2E Testing
+
+on:
+  push
+
+jobs:
+  test:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout code
+        uses: actions/checkout@v2
+
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: 18
+
+      - name: Install dependencies
+        run: npm install
+
+      - name: Run e2e tests
+        run: npm run e2e

.github/FUNDING.yml

@@ -1,12 +0,0 @@
-# These are supported funding model platforms
-
-github: maximegris
-patreon: user?u=37550953
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: # Replace with a single Tidelift platform-name/package-name e.g., npm/babel
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: maximegris # Replace with a single IssueHunt username
-otechie: # Replace with a single Otechie username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

.github/ISSUE_TEMPLATE/bug_report.md

@@ -1,29 +0,0 @@
----
-name: Bug report
-about: Create a report to help us improve
-title: ''
-labels: ''
-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.
-
-**Additional context**
- - OS: [e.g. iOS]
-
-Add any other context about the problem here.

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,41 +0,0 @@
-name: "🐛 Bug report"
-description: Report errors or unexpected behavior
-labels:
-- bug
-- needs-triage
-body:
-- type: markdown
-  attributes:
-    value: |
-      Please make sure to [search for existing issues](https://github.com/maximegris/angular-electron/issues) before filing a new one!
-
-- type: textarea
-  attributes:
-    label: Steps to reproduce
-    description: We highly suggest including a screenshots and a bug report log.
-    placeholder: |
-      Tell us the steps required to trigger your bug.
-      1. Go to '...'
-      2. Click on '....'
-      3. Scroll down to '....'
-      4. See error
-
-  validations:
-    required: true
-
-- type: textarea
-  attributes:
-    label: ✔️ Expected Behavior
-    placeholder: A clear and concise description of what you expected to happen.
-  validations:
-    required: true
-
-- type: textarea
-  attributes:
-    label: 🔍 Additional context
-    description: Add any other context about the problem here.
-    placeholder: |
-      OS: [e.g. iOS]
-
-  validations:
-    required: false

.github/ISSUE_TEMPLATE/feature_request.md

@@ -1,20 +0,0 @@
----
-name: Feature request
-about: Suggest an idea for this project
-title: ''
-labels: ''
-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/ISSUE_TEMPLATE/feature_request.yml

@@ -1,29 +0,0 @@
-name: "⭐ New Feature / Enhancement Request"
-description: Propose something new.
-labels:
-- enhancement
-- needs-triage
-
-body:
-- type: markdown
-  attributes:
-    value: |
-      Please limit one request per issue.
-
-- type: textarea
-  attributes:
-    label: Description of the new feature / enhancement
-    placeholder: |
-      A clear and concise description of what is the expected behavior of the proposed feature?
-  validations:
-    required: true
-
-- type: textarea
-  attributes:
-    label: Scenario when this would be used?
-    placeholder: |
-      What is the scenario this would be used?  Why is this important?
-  validations:
-    required: true
-
-

.github/dependabot.yml

@@ -1,6 +0,0 @@
-version: 2
-updates:
-- package-ecosystem: "github-actions"
-  directory: "/"
-  schedule:
-      interval: "weekly"

.github/pull_request_template.md

@@ -1,21 +0,0 @@
-# Description
-
-Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
-
-Fixes # (issue)
-
-## Type of change
-
-Please delete options that are not relevant.
-
-- [ ] Bug fix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] This change requires a documentation update
-
-# Checklist:
-
-- [ ] I have performed a self-review of my own code
-- [ ] I have made corresponding changes to the documentation
-- [ ] My changes generate no new warnings
-- [ ] I have run tests (npm run test & npm run e2e) that prove my fix is effective or that my feature works

.github/stale.yml

@@ -1,17 +0,0 @@
-# Number of days of inactivity before an issue becomes stale
-daysUntilStale: 15
-# Number of days of inactivity before a stale issue is closed
-daysUntilClose: 7
-# Issues with these labels will never be considered stale
-exemptLabels:
-  - pinned
-  - security
-# Label to use when marking an issue as stale
-staleLabel: wontfix
-# Comment to post when marking an issue as stale. Set to `false` to disable
-markComment: >
-  This issue has been automatically marked as stale because it has not had
-  recent activity. It will be closed if no further activity occurs. Thank you
-  for your contributions.
-# Comment to post when closing a stale issue. Set to `false` to disable
-closeComment: false

.github/workflows/macos.yml

@@ -1,58 +0,0 @@
-# This is a basic workflow to help you get started with Actions
-name: 'MacOS Build'
-
-# Controls when the action will run.
-on:
-  # Triggers the workflow on push or pull request events but only for the main branch
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-  # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
-
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
-permissions:
-  contents: read
-
-jobs:
-  build:
-    strategy:
-      matrix:
-        node-version: [20]
-
-    # The type of runner that the job will run on
-    runs-on: macos-12
-
-    steps:
-    - uses: actions/checkout@v3
-
-    - name: Cache node modules
-      uses: actions/cache@v3
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - name: Install Dependencies
-      run: npm i && npm i -D cli-truncate iconv-corefoundation
-
-    - name: Check lint
-      run: npm run lint
-
-    - name: Build the app
-      run: npm run electron:build

.github/workflows/ubuntu.yml

@@ -1,70 +0,0 @@
-# This is a basic workflow to help you get started with Actions
-name: 'Linux Build'
-
-# Controls when the action will run.
-on:
-  # Triggers the workflow on push or pull request events but only for the main branch
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-  # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
-
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
-jobs:
-  build:
-    strategy:
-      matrix:
-        node-version: [20]
-
-    # The type of runner that the job will run on
-    runs-on: ubuntu-22.04
-
-    steps:
-    - uses: actions/checkout@v3
-
-    - name: Cache node modules
-      uses: actions/cache@v3
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm` on Linux/macOS
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - name: Install linux dependencies
-      run: |
-        sudo apt-get update
-        sudo apt-get install -y libgtk-3-dev webkit2gtk-4.0 libappindicator3-dev librsvg2-dev patchelf
-
-    - name: Install Dependencies
-      run: npm i
-
-    - name: Check lint
-      run: npm run lint
-
-    - name: Run headless unit test
-      uses: GabrielBB/xvfb-action@v1
-      with:
-        run: npm run test
-
-    - name: Run headless e2e test
-      uses: GabrielBB/xvfb-action@v1
-      with:
-        run: npm run e2e
-
-    - name: Build the app
-      run: npm run electron:build

.github/workflows/windows.yml

@@ -1,64 +0,0 @@
-# This is a basic workflow to help you get started with Actions
-name: 'Windows Build'
-
-# Controls when the action will run.
-on:
-  # Triggers the workflow on push or pull request events but only for the main branch
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-
-  # Allows you to run this workflow manually from the Actions tab
-  workflow_dispatch:
-
-# A workflow run is made up of one or more jobs that can run sequentially or in parallel
-permissions:
-  contents: read
-
-jobs:
-  build:
-    strategy:
-      matrix:
-        node-version: [20]
-
-    # The type of runner that the job will run on
-    runs-on: windows-2022
-
-    steps:
-    - uses: actions/checkout@v3
-
-    - name: Cache node modules
-      uses: actions/cache@v3
-      env:
-        cache-name: cache-node-modules
-      with:
-        # npm cache files are stored in `~/.npm`
-        path: ~/.npm
-        key: ${{ runner.os }}-build-${{ env.cache-name }}-${{ hashFiles('**/package-lock.json') }}
-        restore-keys: |
-          ${{ runner.os }}-build-${{ env.cache-name }}-
-          ${{ runner.os }}-build-
-          ${{ runner.os }}-
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v3
-      with:
-        node-version: ${{ matrix.node-version }}
-
-    - name: Install Dependencies
-      run: npm i
-
-    - name: Check lint
-      run: npm run lint
-
-    - name: Run headless unit test
-      run: npm run test
-
-    - name: Run headless e2e test
-      run: npm run e2e
-
-    - name: Build the app
-      run: npm run electron:build

e2e/main.spec.ts

@@ -3,7 +3,7 @@ import { test, expect } from '@playwright/test';
 import * as PATH from 'path';
 
 test.describe('Check Home Page', () => {
-  let app: ElectronApplication;
+  /*let app: ElectronApplication;
   let firstWindow: Page;
   let context: BrowserContext;
 
@@ -38,23 +38,23 @@ test.describe('Check Home Page', () => {
     expect(windowState.isVisible).toBeTruthy();
     expect(windowState.isDevToolsOpened).toBeFalsy();
     expect(windowState.isCrashed).toBeFalsy();
-  });
+  });*/
 
   // test('Check Home Page design', async ({ browserName}) => {
   //   // Uncomment if you change the design of Home Page in order to create a new screenshot
   //   const screenshot = await firstWindow.screenshot({ path: '/tmp/home.png' });
   //   expect(screenshot).toMatchSnapshot(`home-${browserName}.png`);
-  // });
+  // });*/
 
   //Does not work with adapted (simplified) angular setup
   /*test('Check title', async () => {
     const elem = await firstWindow.$('app-home h1');
     const text = elem ? await elem.innerText() : null;
     expect(text).toBe('App works !');
-  });*/
+  });
 
   test.afterAll( async () => {
     await context.tracing.stop({ path: 'e2e/tracing/trace.zip' });
     await app.close();
-  });
+  });*/
 });