developer/galaxy-game
1
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

ui/map-renderer: clarify rationale for synthetic moved-event type

Browse Source 
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 <noreply@anthropic.com>
This commit is contained in:
Ilia Denisov
2026-05-09 00:01:03 +02:00
parent 164f23fbed
commit a3fdcfe9c5
1 changed files with 4 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ui/frontend/src/routes/__debug/map/+page.svelte
+4 -2
View File
@@ -93,8 +93,10 @@
handle.viewport.moveCenter(cx, cy); handle.viewport.moveCenter(cx, cy);
// `MovedEvent.type` is a closed literal union over the // `MovedEvent.type` is a closed literal union over the
// built-in plugin names; `"animate"` is the closest // built-in plugin names; `"animate"` is the closest
// match for a programmatic move and the renderer's // match for a programmatic move. The renderer's
// listeners read only `viewport`. // 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", { handle.viewport.emit("moved", {
viewport: handle.viewport, viewport: handle.viewport,
type: "animate", type: "animate",