yonluandClaude Opus 5
162c68769f
frontend/wailsjs/ is deleted and frontend/bindings/ takes its place — a real TypeScript module tree nested by Go import path, generated by wails3's static analyser rather than by building the app and running it. The @go alias absorbs the constant prefix, so a call site imports '@go/library/library.js' and the codemod over all 93 sites was a specifier rewrite plus splitting @go/models' namespaces into one import per package. The 12 SetContext bindings and the fake `context` model are gone, as Phase 2's ServiceStartup port promised: 272 methods across 12 services, none of them plumbing. @runtime/runtime is now a local shim (src/wails/runtime.ts) over @wailsio/runtime, so the 22 EventsOn imports are untouched. It unwraps v3's WailsEvent into v2's callback shape, which is exact here: nothing in backend/events passes more than one data argument, and v3 only packs arguments into a slice when there is more than one. v3 tells the truth about two things v2 lied about, and that is most of the diff. A Go nil slice really does arrive as JSON null, and a Go named string type really is an enum; v2 typed them as T[] and string. utils/binding.ts states the app's actual contract — an absent list is an empty list — once, at the boundary where it is true, and also drops the CancellablePromise the app never cancels. Four test fixtures widen an enum field back to its value union. Not done, and Phase 5's to fix: frontend/test/support/wails-fake.ts still fakes window.go, which v3 does not have, so `make ui-test` is broken and harness.test.ts fails to compile on EventsEmit. That test also asserts v2 ordering that no longer holds — v3's Events.Emit calls the backend and does not notify in-page listeners at all. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UDCbcCZQepnpSQYJ6SxxZm
34 lines
1.2 KiB
TypeScript
34 lines
1.2 KiB
TypeScript
/**
|
|
* The `@runtime/runtime` seam.
|
|
*
|
|
* 22 files import `EventsOn` from here and nothing else, so rather than
|
|
* rewriting 22 imports to v3's `Events.On` the alias points at this
|
|
* module — which is also what gives the Vitest fake exactly one seam to
|
|
* intercept instead of a `window.runtime` global that v3 does not have.
|
|
* (Plan 009, D4.)
|
|
*
|
|
* The one real difference between the two runtimes is the callback
|
|
* shape: v2 spread an event's data across the callback's arguments,
|
|
* v3 hands over a single `WailsEvent` object. Unwrapping `.data` here
|
|
* reproduces v2's shape for the single-value case, which is every emit
|
|
* in this tree — `backend/events` has no call site passing more than
|
|
* one data argument, and v3's `EventManager.Emit` only packs arguments
|
|
* into a slice when there is more than one, so there is nothing to
|
|
* un-spread.
|
|
*/
|
|
|
|
import { Events } from '@wailsio/runtime';
|
|
|
|
/**
|
|
* EventsOn registers a listener for a backend event and returns the
|
|
* function that unregisters it.
|
|
*/
|
|
export function EventsOn(
|
|
eventName: string,
|
|
callback: (...data: any[]) => void,
|
|
): () => void {
|
|
return Events.On(eventName, (ev) => {
|
|
callback(ev.data);
|
|
});
|
|
}
|