Merge pull request #31 from PiterWeb/main

Bug fixed showing confirm on options navigation always

Author: PiterWeb

README.md

@@ -65,6 +65,8 @@ There is no way to self-host the infrastructure of RemoteController because it h
 
 - If you want to self-host a TURN/STUN server you can [try Coturn](https://github.com/coturn/coturn). (This is only an example, you can choose other STUN/TURN implementations)
 
+- Also you can host the Web version (but it is only frontend) to make like a network of Remote Controller web clients
+
 ## Build
 
 ### Prerequisites

Taskfile.yml

@@ -4,12 +4,41 @@ tasks:
   build:
     cmds:
       - wails build -platform=windows/amd64,windows/arm64,linux/amd64,linux/arm64
-
+    desc: Build the application for all platforms
+  build-win:
+    cmds:
+      - wails build -platform=windows/amd64,windows/arm64
+    desc: Build the application for Windows
+  build-linux:
+    cmds:
+      - wails build -platform=linux/amd64,linux/arm64
+    desc: Build the application for Linux
+  build-wasm-front-linux:
+    cmds:
+      - cd frontend
+      - cd static
+      - cd wasm
+      - GOOS=js GOARCH=wasm go build -o signal.wasm
+    desc: Build the frontend wasm for Linux
+  build-wasm-front-win:
+    cmds:
+      - cd frontend
+      - cd static
+      - cd wasm
+      - powershell.exe -Command { $env:GOOS="js";$env:GOARCH="wasm"; go build -o signal.wasm }
+    desc: Build the frontend wasm for Windows
   dev-all:
     cmds:
       - wails dev
+    desc: Run the application in development mode
 
   dev-front:
     cmds:
       - cd frontend
-      - pnpm run dev
+      - pnpm run dev
+    desc: Run the frontend in development mode
+  test:
+    cmds:
+      - cd frontend
+      - pnpm run test
+    desc: Run the frontend tests

docs/SEO.xlsx

@@ -0,0 +1,12 @@
+/* eslint-disable @typescript-eslint/no-unused-vars */
+import { defineConfig } from "cypress";
+
+export default defineConfig({
+  e2e: {
+    experimentalStudio: true,
+    setupNodeEvents(on, config) {
+      
+      // implement node event listeners here
+    },
+  },
+});

frontend/cypress.config.ts

@@ -0,0 +1,5 @@
+describe('template spec', () => {
+  it('passes', () => {
+    cy.visit('http://localhost:5173/')
+  })
+})

frontend/cypress/e2e/config/languages.cy.ts

@@ -0,0 +1,5 @@
+{
+  "name": "Using fixtures to represent data",
+  "email": "hello@cypress.io",
+  "body": "Fixtures are a great way to mock data for responses to routes"
+}

frontend/cypress/fixtures/example.json

@@ -0,0 +1,37 @@
+/// <reference types="cypress" />
+// ***********************************************
+// This example commands.ts shows you how to
+// create various custom commands and overwrite
+// existing commands.
+//
+// For more comprehensive examples of custom
+// commands please read more here:
+// https://on.cypress.io/custom-commands
+// ***********************************************
+//
+//
+// -- This is a parent command --
+// Cypress.Commands.add('login', (email, password) => { ... })
+//
+//
+// -- This is a child command --
+// Cypress.Commands.add('drag', { prevSubject: 'element'}, (subject, options) => { ... })
+//
+//
+// -- This is a dual command --
+// Cypress.Commands.add('dismiss', { prevSubject: 'optional'}, (subject, options) => { ... })
+//
+//
+// -- This will overwrite an existing command --
+// Cypress.Commands.overwrite('visit', (originalFn, url, options) => { ... })
+//
+// declare global {
+//   namespace Cypress {
+//     interface Chainable {
+//       login(email: string, password: string): Chainable<void>
+//       drag(subject: string, options?: Partial<TypeOptions>): Chainable<Element>
+//       dismiss(subject: string, options?: Partial<TypeOptions>): Chainable<Element>
+//       visit(originalFn: CommandOriginalFn, url: string, options: Partial<VisitOptions>): Chainable<Element>
+//     }
+//   }
+// }

frontend/cypress/support/commands.ts

@@ -0,0 +1,20 @@
+// ***********************************************************
+// This example support/e2e.ts is processed and
+// loaded automatically before your test files.
+//
+// This is a great place to put global configuration and
+// behavior that modifies Cypress.
+//
+// You can change the location of this file or turn off
+// automatically serving support files with the
+// 'supportFile' configuration option.
+//
+// You can read more here:
+// https://on.cypress.io/configuration
+// ***********************************************************
+
+// Import commands.js using ES2015 syntax:
+import './commands'
+
+// Alternatively you can use CommonJS syntax:
+// require('./commands')

frontend/cypress/support/e2e.ts

@@ -0,0 +1,14 @@
+{
+    "extends": "../tsconfig.json",
+    "include": [
+        "../node_modules/cypress",
+        "**/*.ts"
+    ],
+    "compilerOptions": {
+        "noEmit": false,
+        "sourceMap": false,
+        "types": [
+            "cypress"
+        ]
+    },
+}