pastilhasandClaude Opus 5
5d62668883
Top panel: Expert / Intermediate / Beginner. Bottom: that difficulty's saved
games, best first, click to play one on the board.
── the selection lives in the URL ──
`/minesweeper/expert`, not a channel and not panel state. It survives a
refresh, it can be linked, and the two panels never pass anything between
themselves — both read `useParams`. The plugin section route already existed;
nothing had used it.
The side effect hangs off the URL too: an effect on the selected level posts
the difficulty, so arriving at `/minesweeper/expert` by click, deep link or
back button all leave the game on expert. `POST /difficulty` verifies and is
idempotent, so a repeat changes nothing. One `<Navigate replace>` after the
hooks canonicalises both the bare route and a bogus section, and it waits for
`/status` so the URL lands on what the game IS rather than a guess — which is
why `difficulty` is now part of that payload.
Levels are NavLinks so cmd-click works and the active style comes from the
router. Replay rows are buttons, because they do not navigate anywhere, they
make the game do something. That is the line navigation-audit.md draws.
── two things on the server ──
`GET /replays` reads the directory rather than any index, because the filename
IS the metadata — Minesweeper X names a recording `<Lvl> <secs> - <date>.mvr`
and keeps no catalogue. A name that does not parse is skipped rather than
guessed at. Ordering is the server's: a loss is never "best" however short it
was, so wins rank by time and losses fall to the end, still watchable.
`POST /replay` drives Extras > Play Recording... and TYPES the filename into a
file dialog, which is why it only accepts a name `isKnownReplay` just matched
against the directory. An unchecked client string reaching `xdotool type` can
carry a path, a wildcard, or a newline that submits something else. Verified by
the dialog closing, not by the window size — a beginner replay leaves the
window beginner-sized, which is also what nothing-happened looks like.
Verified end to end against the running session: the expert list comes back
ranked 58.63 through 82.06 with losses after, playing 58.63 starts on the
board, and `{"file":"../../../etc/passwd"}` is a 404.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: de3ed4e6-f88a-429c-94e6-a760336ba83b
36 lines
1.5 KiB
TypeScript
36 lines
1.5 KiB
TypeScript
import type { LayoutNode } from 'officerdev';
|
|
|
|
// Two panels stacked on the left, the game on the right — the same arrangement Atelier uses, and the one
|
|
// the rest of the app reads as "controls beside a surface".
|
|
//
|
|
// Difficulty on top, that difficulty's saved games below. 30/70 because the top panel holds exactly three
|
|
// rows and the bottom one is a list that wants the room.
|
|
//
|
|
// Which difficulty is selected lives in the URL (`/minesweeper/expert`), not here and not in a channel, so
|
|
// the two panels never pass it between themselves — they both read `useParams`.
|
|
//
|
|
// The game panel keeps the id `minesweeper` it had when this was a single panel, so any per-panel state
|
|
// already keyed on it survives the change.
|
|
export const defaultLayout: LayoutNode = {
|
|
type: 'group',
|
|
id: 'minesweeper-root',
|
|
direction: 'horizontal',
|
|
children: [
|
|
{
|
|
node: {
|
|
type: 'group',
|
|
id: 'minesweeper-side',
|
|
direction: 'vertical',
|
|
children: [
|
|
{ node: { type: 'panel', id: 'minesweeper-side-top', appType: 'minesweeper-levels' }, size: 30 },
|
|
{ node: { type: 'panel', id: 'minesweeper-side-bottom', appType: 'minesweeper-replays' }, size: 70 },
|
|
],
|
|
},
|
|
// 25 rather than Atelier's 30: the board is drawn at a whole-number scale, so the panel losing a
|
|
// quarter of its width can drop it a step. 75% of a typical panel still clears 2x.
|
|
size: 25,
|
|
},
|
|
{ node: { type: 'panel', id: 'minesweeper', appType: 'minesweeper' }, size: 75 },
|
|
],
|
|
};
|