From a3fdcfe9c512707ad2b732cdd9ac3bd48afa72a1 Mon Sep 17 00:00:00 2001 From: Ilia Denisov Date: Sat, 9 May 2026 00:01:03 +0200 Subject: [PATCH] ui/map-renderer: clarify rationale for synthetic moved-event type MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Expanding the comment so future readers know the `type` field is informational here — no `pixi-viewport@6` plugin or local listener switches on it, so picking any literal from the closed union works. Co-Authored-By: Claude Opus 4.7 --- ui/frontend/src/routes/__debug/map/+page.svelte | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/ui/frontend/src/routes/__debug/map/+page.svelte b/ui/frontend/src/routes/__debug/map/+page.svelte index 9b0b907..3e34dc9 100644 --- a/ui/frontend/src/routes/__debug/map/+page.svelte +++ b/ui/frontend/src/routes/__debug/map/+page.svelte @@ -93,8 +93,10 @@ handle.viewport.moveCenter(cx, cy); // `MovedEvent.type` is a closed literal union over the // built-in plugin names; `"animate"` is the closest - // match for a programmatic move and the renderer's - // listeners read only `viewport`. + // match for a programmatic move. The renderer's + // listeners (and `pixi-viewport@6`'s own plugins) + // read only `viewport` — no consumer switches on + // `type`, so the choice is informational. handle.viewport.emit("moved", { viewport: handle.viewport, type: "animate",