(76d10d7) Strike through a relation to a discarded ticket, and bump to 0.31.5
The relations block marked a target `○ ◐ ●` or `?`, and none of those can say the target was discarded: the status mark is one cell in a column of five states, and `●` in grey against `●` in green is a colour a pipe does not get. A row pointing at abandoned work therefore read as a live dependency, which is exactly what it is not. The row is struck through instead, the whole of it, gutter and padding included, so the line runs unbroken from the label to the end of the title. The relation stays recorded, for completeness and for the case the target is moved back out of discarded, and reads at a glance as no longer standing for anything. The mark column is untouched: 451fb83 already gave a discarded target the full circle of done in the grey of the untouched pile, and the strike is additive on top of that. `Cell` learns a modifier, the first style on it that is not a colour. Same trick as the palette, one step further: `Modifier::ansi()` is SGR 9 and `From<Modifier> for ratatui::style::Modifier` is `CROSSED_OUT`, so a style that exists for one renderer and not the other is a compile error. Bold stays out of it, because bold rides inside `Color::Magenta.ansi()` and `span_from` adds it back from the colour alone; a second modifier goes beside this one. `paint_cell` opens the modifier ahead of the colour and closes both with one reset, which is why the reset is now a constant the two writers share rather than a literal in `paint`. `span_from` takes the modifier too and has no early return for the uncoloured case any more: a struck plain run is a styled span with no foreground. `Cell::struck` is a builder, because the strike is decided a whole row at a time by the layout that already chose the colours. `Body::push_cell` merges on the whole style rather than the colour alone. Nothing outside the relations block carries a modifier today, and a merge keyed on the colour would silently strike a plain run through the moment one did. The strike is under the same flag every other escape is, so a piped `show` carries none of it. That is the bargain committed and reviewing already take for being told apart by colour alone, and `assets/SKILL.md` says so outright rather than leaving an agent to infer that a plain-looking row may point at abandoned work. Tests are paired both ways, and both halves are load bearing: a renderer that struck nothing fails the presence, and one that struck every row fails the absence. `the_status_marks_are_pinned` had never listed discarded, so it does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
d1a0f0ee27
commit
7994d98913
@@ -231,6 +231,10 @@ pair shares a glyph, and **your output is a pipe, so you do not get the colour**
|
||||
`◐` as under way and `●` as nothing left to do, and if it matters which of the two,
|
||||
`worklane show` on that target says so in its Status field. `○` is unambiguous without it.
|
||||
|
||||
A row pointing at a **discarded** target is struck through on a terminal, since a
|
||||
relation to abandoned work otherwise reads as a live dependency. That is a style rather
|
||||
than a character, so a pipe does not get it either: ask the target's Status field.
|
||||
|
||||
## Campaigns
|
||||
|
||||
A campaign groups the tickets that have to be finished together: a release, a migration,
|
||||
|
||||
Reference in New Issue
Block a user