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.
91 lines
2.6 KiB
Go
91 lines
2.6 KiB
Go
package events
|
|
|
|
import (
|
|
"context"
|
|
"errors"
|
|
"log/slog"
|
|
|
|
"github.com/wailsapp/wails/v2/pkg/runtime"
|
|
)
|
|
|
|
// ErrNoRuntime is returned by Deliver when the context carries neither
|
|
// a test Sink nor a live Wails runtime, so the event went nowhere.
|
|
var ErrNoRuntime = errors.New(
|
|
"no Wails runtime or event sink in context",
|
|
)
|
|
|
|
// Sink receives events in place of the Wails runtime.
|
|
//
|
|
// Installing one with WithSink is what makes a service that emits
|
|
// events testable in-process: see Deliver for why the real runtime
|
|
// cannot be used there.
|
|
type Sink interface {
|
|
Emit(name string, data ...any)
|
|
}
|
|
|
|
// sinkKey is the private context key an installed Sink is stored under.
|
|
type sinkKey struct{}
|
|
|
|
// WithSink returns a context whose events are recorded by sink rather
|
|
// than pushed to the frontend.
|
|
//
|
|
// The sink travels in the context rather than in a package-level
|
|
// variable so that parallel tests cannot observe each other's events
|
|
// and so that production emits pay no synchronisation cost.
|
|
func WithSink(ctx context.Context, sink Sink) context.Context {
|
|
return context.WithValue(ctx, sinkKey{}, sink)
|
|
}
|
|
|
|
// sinkFrom returns the Sink installed in ctx, or nil.
|
|
func sinkFrom(ctx context.Context) Sink {
|
|
sink, _ := ctx.Value(sinkKey{}).(Sink)
|
|
|
|
return sink
|
|
}
|
|
|
|
// Emit publishes a Wails event, tolerating any context.
|
|
//
|
|
// This is the only supported way to emit an event: nothing outside this
|
|
// package may call runtime.EventsEmit, which TestNoDirectEventsEmit
|
|
// enforces.
|
|
//
|
|
// runtime.EventsEmit calls log.Fatalf when the context is nil or lacks
|
|
// the runtime's "events" value, terminating the process rather than
|
|
// returning an error. Background workers that outlive a context, and
|
|
// any test that constructs a service directly, both hit that path — so
|
|
// an event with nowhere to go is dropped and logged here instead.
|
|
func Emit(ctx context.Context, name string, data ...any) {
|
|
if err := Deliver(ctx, name, data...); err != nil {
|
|
slog.Default().Debug(
|
|
"dropping event, no Wails runtime in context",
|
|
"event", name,
|
|
)
|
|
}
|
|
}
|
|
|
|
// Deliver is Emit for the one caller that must know whether delivery
|
|
// happened: the dev control surface (backend/testctl), whose whole
|
|
// purpose is to impersonate a backend emit and which would otherwise
|
|
// report success for an event that went nowhere.
|
|
//
|
|
// Ordinary emitters want Emit.
|
|
func Deliver(ctx context.Context, name string, data ...any) error {
|
|
if ctx == nil {
|
|
return ErrNoRuntime
|
|
}
|
|
|
|
if sink := sinkFrom(ctx); sink != nil {
|
|
sink.Emit(name, data...)
|
|
|
|
return nil
|
|
}
|
|
|
|
if ctx.Value("events") == nil {
|
|
return ErrNoRuntime
|
|
}
|
|
|
|
runtime.EventsEmit(ctx, name, data...)
|
|
|
|
return nil
|
|
}
|