Provisioning check values are shown without units #90

Closed
opened 2026-10-08 19:11:24 -04:00 by goddard · 1 comment
Collaborator

Check results show raw values without units, so some are hard to read.

  • The game status check's observed value is the player count (native.ts:728), shown as "Observed 0".
  • The Plutonium checks show revisions as bare numbers, e.g. "4847" (native.ts:742-748).
  • ProvisioningProgress.svelte:68-70 prints expected and actual as-is for every check.

Screenshots

From the synthetic UI preview. Progress records and a launch recipe were added to the disposable fixture database using the labels the worker records. "After" images are mockups made in an uncommitted copy.

Before:
Before

After (mockup):
After (mockup)

Fix

  • Format check values per check type, e.g. "0 players" and "r4847"
Check results show raw values without units, so some are hard to read. - The game status check's observed value is the player count (`native.ts:728`), shown as "Observed 0". - The Plutonium checks show revisions as bare numbers, e.g. "4847" (`native.ts:742-748`). - `ProvisioningProgress.svelte:68-70` prints `expected` and `actual` as-is for every check. **Screenshots** _From the synthetic UI preview. Progress records and a launch recipe were added to the disposable fixture database using the labels the worker records. "After" images are mockups made in an uncommitted copy._ Before: ![Before](https://gitea.thewrightserver.net/attachments/9b3886db-0e2a-4dc8-9059-92d890d8d487) After (mockup): ![After (mockup)](https://gitea.thewrightserver.net/attachments/77367946-69c4-42af-b196-7eb482202e19) **Fix** - Format check values per check type, e.g. "0 players" and "r4847"
goddard added the
priority
low
type/ux
labels 2026-10-08 19:11:24 -04:00
josh was assigned by goddard 2026-10-08 19:11:24 -04:00
Author
Collaborator

Reviewed 6128a137cc. The fix is done, so I'm closing this.

Checklist

  • Values formatted per check. provisioningCheckValue (provisioning-presentation.ts:6-11) shows the game check as a player count using countLabel ("0 players", "1 player"), and both Plutonium checks as revisions ("r4847"). ProvisioningProgress.svelte:69-70 uses it for expected and observed values. Other values, such as maps and container states, are unchanged.

Review notes

  • Every numeric check the worker records is covered. occupancy is the only other check key, and nothing records it.
  • In the synthetic preview, the checks read "0 players" and "r4847".
  • The 4 related test files pass locally (210 tests), and npm run check reports 0 errors.
  • Minor and non-blocking: provisioningCheckValue has no unit test.
Reviewed 6128a137cc3ab1495f7239ccc7cab05773fb2313. The fix is done, so I'm closing this. **Checklist** - [x] **Values formatted per check.** `provisioningCheckValue` (`provisioning-presentation.ts:6-11`) shows the game check as a player count using `countLabel` ("0 players", "1 player"), and both Plutonium checks as revisions ("r4847"). `ProvisioningProgress.svelte:69-70` uses it for expected and observed values. Other values, such as maps and container states, are unchanged. **Review notes** - Every numeric check the worker records is covered. `occupancy` is the only other check key, and nothing records it. - In the synthetic preview, the checks read "0 players" and "r4847". - The 4 related test files pass locally (210 tests), and `npm run check` reports 0 errors. - Minor and non-blocking: `provisioningCheckValue` has no unit test.
Sign in to join this conversation.