logan
5ca6cad45a
A coding agent could develop this repo's Go packages and could not develop the application: every path to running YellowJacket ended in a blocking GTK window, so 265 bound methods, 46 events, 33 component directories and 13 stores had exactly one form of verification available — `tsc --noEmit`. The unlock is that `wails dev`'s dev server on :34115 serves the real frontend with the real generated bindings against the same Go backend a desktop window attaches to, so a plain Chromium under Xvfb gets a fully functional app. Four test tiers now exist, cheapest first: - `make ui-test` — 313 Vitest tests in a real browser in ~2 s, no app, no backend, no display. Works because `frontend/wailsjs/` is a pure passthrough to `window.go`/`window.runtime`, so faking just those two globals runs the real bindings and the real store code. - `make test` — services in-process, asserting on the payload the frontend would receive, via a new `events.Emit` wrapper. - `make dev-headless` + `playwright-cli` — the real app, driven interactively, with an event bridge on `window.__yjEvents` and a dev-only control surface at `/__test/`. - `make e2e` — 19 of those flows frozen as Playwright specs. `events.Emit(ctx, …)` replaces all 35 direct `runtime.EventsEmit` call sites: wails' `getEvents` `log.Fatalf`s on any context without its runtime, so those paths could not run under test and a background worker could take the app down. Four packages had each hand-rolled the same guard; nine more guarded on `ctx != nil`, which does not help. `TestNoDirectRuntimeEmits` fails the build on a new one. Fixtures are generated, not committed (`make testdata`), and seeds are built by *running the app* — never by hand-writing config and DB rows, which would be a second description of a valid YJ_HOME. `.gitea/workflows/ci.yml` is the first workflow here that tests anything; the other three only package, so `gitea_ci` reported only packaging jobs and misled anyone asking whether a push was healthy. Both jobs were prototyped to green in a bare ubuntu:24.04 container before the YAML was written, which immediately caught `make lint` linting three configurations that nothing builds: all three passes omitted `webkit2_41`, so wails resolved webkit2gtk-4.0 — which Arch still ships and Ubuntu 24.04 dropped. Operational instructions live in `.pi/skills/yellowjacket-dev/`, measured discoveries in `.planning/NOTES.md`, and architecture in `CLAUDE.md` — split by tense, not by topic, because a topical split gives every new fact two plausible homes. `make skill-check` fails a commit if the skill cites a make target that does not exist.
52 lines
2.6 KiB
JSON
52 lines
2.6 KiB
JSON
{
|
|
"compilerOptions": {
|
|
// base options
|
|
"esModuleInterop": true, // Helps mend a few of the fences between CommonJS and ES Modules.
|
|
"skipLibCheck": true, // Skips checking the types of .d.ts files. This is important for performance, because otherwise all node_modules will be checked.
|
|
"target": "esnext", // The version of JavaScript you're targeting.
|
|
"allowJs": true, // Allows you to import .js files.
|
|
"moduleDetection": "force", // This option forces TypeScript to consider all files as modules. This helps to avoid 'cannot redeclare block-scoped variable' errors.
|
|
"isolatedModules": true, // This option prevents a few TS features which are unsafe when treating modules as isolated files.
|
|
"verbatimModuleSyntax": true, // This option forces you to use import type and export type, leading to more predictable behavior and fewer unnecessary imports.
|
|
// strictness
|
|
"strict": true, // Enables all strict type checking options.
|
|
"noUncheckedIndexedAccess": true, // Prevents you from accessing an array or object without first checking if it's defined.
|
|
"noImplicitOverride": true, // Makes the override keyword actually useful in classes.
|
|
// optional "noisy" options
|
|
"noImplicitReturns": true,
|
|
"noUnusedLocals": true,
|
|
"noUnusedParameters": true,
|
|
"noFallthroughCasesInSwitch": true,
|
|
// transpiling to js options
|
|
"module": "esnext", // Tells TypeScript what module syntax to use.
|
|
"outDir": "dist", // Tells TypeScript where to put the compiled JavaScript files.
|
|
// running in the DOM
|
|
"lib": ["esnext", "dom", "dom.iterable"], // Tells TypeScript what built-in types to include.
|
|
// module resolution
|
|
"moduleResolution": "bundler",
|
|
"paths": { // path aliases to find modules
|
|
"@go/*": ["./wailsjs/go/*"],
|
|
"@components/*": ["./src/components/*"],
|
|
"@assets/*": ["./src/assets/*"],
|
|
"@pages/*": ["./src/pages/*"],
|
|
"@runtime/*": ["./wailsjs/runtime/*"],
|
|
"@utils/*": ["./src/utils/*"],
|
|
"@store/*": ["./src/store/*"],
|
|
"@test/*": ["./test/*"]
|
|
},
|
|
"types": ["vite/client", "@vitest/browser-playwright"],
|
|
// needed for Lit Elements
|
|
"experimentalDecorators": true,
|
|
"useDefineForClassFields": false, // allows us to define properties as class fields
|
|
// plugins
|
|
"plugins": [
|
|
{"name": "ts-lit-plugin"},
|
|
{"name": "typescript-lit-html-plugin"}
|
|
]
|
|
},
|
|
"include": ["src", "wailsjs", "test"],
|
|
// Wails-generated JS stubs use @ts-check with untyped patterns that
|
|
// violate strict mode. The companion .d.ts files provide the types.
|
|
"exclude": ["wailsjs/go/**/*.js"]
|
|
}
|