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

docs(ui): F8-05 — sync inspector topic docs with the new compact rows
Tests · UI / test (pull_request) Successful in 11m1s
Details

Browse Source 
- order-composer.md describes the production row's apply-gate (two
  selects + ✓/✗) and the click-to-edit entry point for planetRename.
- cargo-routes-ux.md replaces the four-slot grid description with the
  new single-row dropdown + contextual actions and notes the
  "stays on the picked type" UX rule.
- science-designer-ux.md updates the production-picker integration
  description to the dropdown pair and refreshes the e2e walkthrough
  step.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
This commit is contained in:
Ilia Denisov
2026-05-27 13:41:44 +02:00
parent 4a23c357e5
commit aee5f39a7e
3 changed files with 60 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files
ui/docs/science-designer-ux.md
+18 -14
View File
@@ -74,22 +74,26 @@ which surfaces as `rejected` in the order tab.
## Production-picker integration
The planet inspector's Research sub-row
(`lib/inspectors/planet/production.svelte`) renders the four tech
buttons and one extra button per defined science from the player's
`localScience` overlay. A click on a science button dispatches
The planet inspector's production row
(`lib/inspectors/planet/production.svelte`) is two `<select>`s
plus a green ✓ apply / yellow ✗ cancel pair after F8-05. With
the primary picker on `research`, the secondary picker lists the
four tech display strings and one extra option per defined
science from the player's `localScience` overlay. Picking a
science target and pressing ✓ dispatches
`setProductionType("SCIENCE", "<scienceName>")`, mirroring the
wire-level `CommandPlanetProduce` shape
(`pkg/schema/fbs/order.fbs.CommandPlanetProduce`).
The active highlight is derived from `planet.production` — the
display string the engine emits in the report. A science name
shadows the matching tech display string when they collide (a
science deliberately named `Drive` wins over the Drive tech
button), because the wire string is ambiguous and the user clearly
intended the named science. This is a pragmatic accept; a
structured production tag on the wire would let us disambiguate
without the shadow rule, but that is a separate backend concern.
The active value of both selects is derived from
`planet.production` — the display string the engine emits in the
report. A science name shadows the matching tech display string
when they collide (a science deliberately named `Drive` wins over
the Drive tech option), because the wire string is ambiguous and
the user clearly intended the named science. This is a pragmatic
accept; a structured production tag on the wire would let us
disambiguate without the shadow rule, but that is a separate
backend concern.
## Tests
@@ -102,5 +106,5 @@ without the shadow rule, but that is a separate backend concern.
fractions, view-mode Delete dispatches `removeScience`,
duplicate-name guard against the overlay.
- `tests/e2e/sciences.spec.ts` — full Playwright walkthrough:
create → list → set planet production via the Research sub-row
→ delete.
create → list → set planet production via the research/target
dropdown pair + ✓ apply → delete.