Collapsible lanes — frontmatter-backed slim strips outside the width division
A lane folds to a fixed slim vertical strip carrying its glyph, its card-count badge and its title turned on its side, and the strip is deliberately not part of the window's division: the expanded lanes' units divide what is left once each folded strip's fixed width has come off the top, so folding a lane is a re-divide trigger of the Show/Hide Trash family — the window never moves and the siblings grow into what the lane gave up. The state is a first-class lane frontmatter key, `collapsed: true`, and document state exactly as `width` is: the files are the board, so an agent folds a lane by writing one key. Absent means expanded, expanding removes the key rather than writing `false` (the remove-at-default family beside a one-unit `width`, the empty rename's `title` and the None well's `background`), and the lane's `width` rides along untouched so expanding restores the lane the user had. The read is `width`'s leniency one type over — a boolean scalar or a quoted boolean word reads as itself, everything else has no reading at all and renders as expanded, bytes preserved either way. Toggling is the header's always-visible collapse chevron, the lane context menu's single Collapse Lane / Expand Lane row, and a plain click anywhere on the strip; a modified click on the strip stays the ordinary selection grammar, so a folded lane is still selectable by pointer. The title reads bottom-up and is justified to the top of the room below the strip's chrome (owner ruling 2026-08-08), truncating against the strip's own height. While folded the lane draws no cards at all, which is what makes every exclusion true by construction rather than by a guard per gesture: no card face means no marquee target and no navigation frame, and no registered grid means the masonry's drop zones have nothing to resolve against. What did need code is the half that names absolute destinations — the option-arrow jumps and the arrow seed scan past a folded lane, the lane domain's down-arrow is inert on one, and New Card skips it (a selection inside one falls through to the last-active lane, the stale selection's rule). A drop on the strip appends at the lane's end, cards and Finder files alike, with an accent edge standing in for the shadow the strip has no masonry to open; there is no hover-to-auto- expand yet. Lane reorder works on the strip, and a dragged folded lane carries its fold, so its shadow and its replica are the strip rather than its units. The write is `writeLaneWidths` clause for clause — one `updateIndex` bracket, the same stamp behaviour, the same three do-nothing paths — with two new `WriteOperation` cases and two new undo verbs rather than one of each, because a banner or an Edit-menu row that said "resize" after Collapse Lane would name a control the user never touched. Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
This commit is contained in:
@@ -26,6 +26,13 @@ private func baseBoard(_ fixture: WriterFixture) throws {
|
||||
try fixture.card(Ident.card2, in: Ident.lane1, order: "2048", title: "Ship it")
|
||||
}
|
||||
|
||||
/// The base board with its first lane already folded — the "before" an Expand needs
|
||||
/// (03-board-ui.md § Lane ▸ Collapsed lanes).
|
||||
private func baseBoardWithFoldedTodo(_ fixture: WriterFixture) throws {
|
||||
try baseBoard(fixture)
|
||||
try fixture.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\ncollapsed: true\n---\n\n")
|
||||
}
|
||||
|
||||
/// A UUID-shaped name `Ident` does not already spend on the base board — the trash suites need one
|
||||
/// more identity than the fixture offers, and reusing a live card's would be a duplicate the loader
|
||||
/// would rightly withhold.
|
||||
@@ -184,6 +191,36 @@ struct CommitMessageSingleEventTests {
|
||||
#expect(message == "Resize lane 'Todo' to 2×")
|
||||
}
|
||||
|
||||
/// **The fold has its own two words** (03-board-ui.md § Lane ▸ Collapsed lanes; 06 ▸ Commit
|
||||
/// messages' vocabulary), told apart by diff shape alone exactly as the trash pair is.
|
||||
@Test("A folded lane is a Collapse, and an unfolded one an Expand")
|
||||
func collapsingALane() throws {
|
||||
let collapsed = try compose { fixture in
|
||||
try fixture.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\ncollapsed: true\n---\n\n")
|
||||
}
|
||||
#expect(collapsed == "Collapse lane 'Todo'")
|
||||
|
||||
let expanded = try compose(
|
||||
board: { fixture in
|
||||
try baseBoardWithFoldedTodo(fixture)
|
||||
},
|
||||
change: { fixture in
|
||||
try fixture.lane(Ident.lane1, order: "1024", title: "Todo")
|
||||
}
|
||||
)
|
||||
#expect(expanded == "Expand lane 'Todo'")
|
||||
}
|
||||
|
||||
/// The narrator composes off the **reading**, not the key: `collapsed: false` beside an absent key
|
||||
/// moves no lane on screen, so it is the "sequence, not raw `order`" discipline one field over.
|
||||
@Test("A `collapsed: false` that changes no lane composes nothing")
|
||||
func anExplicitFalseIsNotAnEvent() throws {
|
||||
let message = try compose { fixture in
|
||||
try fixture.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\ncollapsed: false\n---\n\n")
|
||||
}
|
||||
#expect(message == ChangeNarrator.unnamedSubject)
|
||||
}
|
||||
|
||||
@Test("An attachment composes Attach, named by the card it landed on")
|
||||
func attachingAFile() throws {
|
||||
let message = try compose { fixture in
|
||||
|
||||
Reference in New Issue
Block a user