Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
f0f88025f3 | ||
|
|
00a64adca8 | ||
|
|
0f0767ac00 | ||
|
|
7994d98913 | ||
|
|
d1a0f0ee27 |
@@ -171,9 +171,21 @@ and this file is for what someone changing worklane's own code needs.
|
||||
### Relating Tickets
|
||||
|
||||
- **The Relations section is `relate`'s alone.** `RELATIONS` is in the section table but deliberately out of `section_args`, so `set` and `append` cannot reach it: a relation names a target that has to be resolved to a uuid first, and a prose flag would let an unresolvable line into the one section that is read back by machine. Same rule as Owner and Status, one field one writer
|
||||
- **`relate --clear <kind> <target>` is the removal, and it is on `relate` rather than on `set`** for the same reason the section is absent from `section_args`: one writer owns both directions, the way `chown` owns setting an owner and clearing one. It names the target and not just the kind, because a ticket can hold several relations of one kind and emptying all of them is not what anybody is asking for. That is also why it is not spelled like `set --clear`, which names a field and empties the whole of it
|
||||
- **The two values are one flag, so clap cannot type them apart.** `num_args = 2` is per occurrence, which is what makes an odd number a usage error and every chunk a full pair; `RelateArgs::cleared` splits the pairs and parses the kind, so a bad kind is refused before the ticket is resolved. It exits 1 rather than clap's 2, which is the price of a two-value flag and the reason `RelationKind::parse_value` names the three in its message
|
||||
- **Both spellings of the kind are accepted**, `blocked-by` from the flag and `blocked by` from the label. Both are in front of the reader: the flag is what recorded the relation and the label is what `show` prints and what the file stores, so refusing the printed form would be a trap for anyone clearing a row they just read. `RelationKind::flag` is a match rather than `label().replace(' ', "-")`, so the flag, the `--clear` value and the completion list cannot drift apart
|
||||
- **`find_relation` searches the ticket's own edges before the board, and that order is the feature.** A dangling edge is the case most likely to need clearing, and no search of the board can reach a target whose ticket is gone, so the id-prefix tier over the stored targets is the only one that finds it. `MIN_ID_SEARCH` is the floor `resolve_in` puts under its own id tier and the comparison is case insensitive for the same reason. Two stored targets under one prefix name the candidates rather than guessing, which is what an ambiguous ticket search already does
|
||||
- **An edge the ticket does not hold reports no change; a target naming nothing at all is an error.** The two are different facts: the first is the state the caller asked for, and the second is a typo that reporting no change would swallow. The resolver's own reason is carried through, so an ambiguous search says so instead of being reported as nothing found
|
||||
- **Recording and clearing the same relation in one call is refused, and the check runs on what was *asked* for.** `items` drops the additions already in the file, so comparing against that would let `--blocked-by X --clear blocked-by X` quietly remove an existing X. `requested` is the full list for exactly that reason. The refusal is `set --clear`'s: nothing is written rather than one direction silently winning
|
||||
- **Removals rewrite the section and additions are appended to the result, in that order.** Two passes rather than one rebuild, so a call with no `--clear` takes exactly the path it always took and `append_section_body` goes on deciding where a new line lands. Rewriting from the parsed relations is lossless because a line that is not a relation is already an error. The last edge leaves `clear_section_body`'s placeholder, which is the line `append` treats as no content, so the next `relate` replaces it instead of writing under it
|
||||
- **A relation is not logged, either direction.** `relate` writes no history entry and neither does `--clear`, which keeps the two consistent; per the history rule, an edge that matters enough to explain gets a comment. Do not add an entry for the removal alone: a log that recorded only the destructive half would read as though the additions had never happened
|
||||
- **`add` does not write the section.** The plan on 4179958 asked for it in the ticket writer; it is out on purpose. A `_No relations._` block in every new ticket is noise in every `show`, and the insertion path has to exist regardless for every ticket written before the section did, so leaving it out means one path that is always exercised rather than two
|
||||
- **The full uuid is stored, not the seven characters `ls` prints.** It resolves without a scan and cannot turn ambiguous as the board grows. `show` renders the short id and the target's title instead: the file is the machine's copy, the output is the reader's
|
||||
- **One direction is stored and the inverse is derived.** `blocked by` goes on the gated ticket rather than `blocks` on the blocker, because the gated ticket is the one whose move is refused and whose author knows about the dependency. `relates to` is symmetric and is written once, on whichever end the caller ran it from. `RelationIndex::inbound` finds the far end by scanning, which is what keeps `relate` a single-file write
|
||||
- **A derived row that reads exactly like a stored one is dropped, and the stored one is kept.** Both ends of a symmetric relation could hold a line, since nothing stopped it until 03bdc76, and the block then drew the same neighbour twice under the same label. The stored row survives because it is the line `relate --clear` can address; the derived one is on a file this ticket does not own
|
||||
- **The dedupe keys on the label and the target, not the kind and the target.** Two tickets each blocking the other is two facts and the block says both, `blocked by` from this end and `blocks` from the other; keying on the kind would fold them into one row and lose half of what the ticket says. Only a symmetric kind can collide with its own stored line, and `RelationKind::is_symmetric` derives that from `label() == inverse_label()` rather than naming `RelatesTo`, so a kind added later answers by construction
|
||||
- **`relate` also refuses to store the mirror, which is the other half of the same fix.** The dedupe repairs a board that already holds both directions; the refusal stops it recurring. `mirrored` in `cmd_relate` reads the target's own relations and reports no change, gated on `is_symmetric` because a target holding `blocked by <this>` is a cycle rather than a duplicate. 4179958 decided `relates to` is written once and not onto both files; for six months nothing enforced it
|
||||
- **A symmetric edge is cleared from the end that stores it.** With both ends holding a line, `--clear` on one leaves the other's, which then draws as the derived row: correct, since the far end still asserts the relation, and the reason the dedupe keeps the stored row rather than the derived one
|
||||
- **A line in the section that is not a relation is an error naming the ticket**, not a line quietly dropped. Nothing but `relate` writes there, so a bad line means a hand-edited file. The TUI is the deliberate exception: `detail_of` falls back to no block, since one corrupt ticket must not take the whole board down
|
||||
- **The block is built outside `content_trim` and passed in.** Half of it comes from other tickets and `content_trim` has only the body. It is spliced over the stored lines where the file has the section, and injected ahead of the metadata where it does not, because a ticket that is only pointed at has no section of its own and still has relations to show
|
||||
- `ensure_section` inserts against `SECTION_ORDER`, before the first following section that is actually in the file, and adds no blank line that was not already there. A handwritten `## Notes` between the plan and the metadata therefore keeps its place, and Metadata is in that list as an anchor rather than as something anything appends to
|
||||
@@ -235,9 +247,12 @@ and this file is for what someone changing worklane's own code needs.
|
||||
- The draw aligns the focused column again on its own geometry, so a resize between keypress and frame cannot hide the selection, and caps every column against blank space past its last card. The stored value may go stale after a tick shrinks the column; that is fine, because what is drawn is corrected immediately and the next navigation writes the correction back
|
||||
- Entering another column follows the selection rather than resetting to its top. The card index carries across columns, so a reset would open the column with the highlight below the fold whenever it was — the opposite of the detail view's reset-on-selection-move, where each ticket genuinely starts at its own top. The index is shared and clamps permanently when a shorter column pulls it down, so a column you return to follows the selection to where it now sits rather than holding your old place
|
||||
- **The footer names only keys that work.** It read `↑↓ scroll` when nothing scrolled at all, which sends the reader looking for their own mistake. A UI that misdescribes itself is worse than one that is merely incomplete
|
||||
- **A hint is a key and what pressing it does, and `key_hint` is the only thing that draws one.** The key is cyan and bold, the description takes the terminal's default foreground, and the row keeps its three-space gaps. Everything that names a key goes through it: the three footer states, the prompt's two keys, the picker's row and the `q board` on the frame's border, so a reader learns the shape once. Same division in frig and pantop, each in its own accent colour, cyan here and magenta there — the three tools are read side by side and used to look like three programs
|
||||
- **A key that is its description's first letter is merged into it**, so the board draws `quit`, `campaign` and `tag` with the letter coloured and no letter in front, while `y copy id`, `ctrl-c quit`, `d show done (2)` and every arrow row stay split. Two cells back on a row already at its width naming eight keys, and the coloured letter *is* the key either way. The prefix test in `key_hint` is case sensitive for exactly that reason: a row naming both `r` and `R` would otherwise draw one word for the two of them, and the merged form can only say which key it is while the letter on screen is that key. It also means the row carries both forms at once, which is the cost of the two cells
|
||||
- **What the row is cannot be read off its text any more, so the tests read its cells.** `footer_cells`, `footer_at`, `keys_on` and `footer_style` in the test module: `keys_on(.., "quit")` is `Some(1)` where `q` quits and `Some(0)` on a row whose only `quit` is the tail of `ctrl-c quit`. A `contains("q quit")` cannot tell those apart, and three of the guards that keep 1b78a24 out were written that way
|
||||
- **`q` and `esc` are one key: close what is open, quit when there is nothing left to close.** `q` used to set `should_quit` outright, so a reader who pressed it to put a ticket away lost the board instead, which is not what `q` does anywhere else that lays a document over a list. One match arm in `main.rs`, not two: two arms carrying one rule is how a later edit changes it for one key and not the other
|
||||
- **The rule is `Board::dismiss`, not the match arm.** The dispatch in `main.rs` is not reachable from a test, so anything decided there is undecidable by the suite. The arm is the line that names the keys and nothing else. `the_dispatch_gives_q_and_esc_one_arm_and_leaves_ctrl_c_quitting` scans `main.rs` for what the arm cannot say for itself, over whitespace-collapsed source so rustfmt cannot fail it
|
||||
- **The footer's last slot always answers how to get out**, and with a ticket open the honest answer is `ctrl-c`, the only key left that quits in one press. Going on saying `q quit` there would be 1b78a24 in the other direction: a footer describing a key by what it used to do
|
||||
- **The footer's last slot always answers how to get out**, and with a ticket open the honest answer is `ctrl-c`, the only key left that quits in one press. Going on drawing the merged `quit` there would be 1b78a24 in the other direction: a footer describing a key by what it used to do. `ctrl-c quit` is split by the same rule that merges the other, being no word's first letter
|
||||
- **The overlay names its ticket on the border, not at the head of the paragraph.** `Board::detail` is a `Detail` carrying the title, the id and the text, because the name has to travel beside the body rather than inside it: `content_trim` drops the `# ` heading on purpose, since `cmd_show` prints it, and anything in the paragraph scrolls away
|
||||
- `detail_title` cuts the string itself instead of leaving it to ratatui, which truncates an overlong block title at whatever cell it reaches and would take the id with it. Cut against the inner width, so the id survives whole and the name ends in an ellipsis. The id goes first because that is how every other view addresses a ticket
|
||||
- The detail view renders from cells, never from painted strings: ratatui draws styled spans, so an escape sequence in a paragraph would be printed as literal bytes. `content_trim` and `format_history_with` take the colour decision for the CLI's side of the same layouts
|
||||
@@ -256,23 +271,27 @@ and this file is for what someone changing worklane's own code needs.
|
||||
- **A campaign the board does not hold labels nothing**, the answer `mark_blocked` gives a dangling blocker. `campaign_cells` renders that case as `_missing_` because a metadata table is a place to report a dangling reference; a card is not
|
||||
- **`c` opens the campaign picker, and taking a campaign filters the tab's columns to its members.** Not a fifth tab: a campaign groups across the flow, so the shape of the answer is the statuses with fewer cards in them, which is what `campaign show` already answers the question in. Every column is kept, empty ones included. The filter is applied in `reload`, where the columns are built, so nothing downstream has to ask whether a campaign is selected — the board simply holds fewer cards, and `first_match`, `column_count` and the copy key all keep working unchanged
|
||||
- **`Tab::campaign` is a uuid on the tab, not on the `Board`.** A campaign belongs to one `.worklane`, so a filter carried onto another project's tab would empty it and say nothing about why. It is looked up by uuid rather than held as an index, and a selection whose campaign has left the board is cleared by `reload` rather than left filtering the board to nothing
|
||||
- **The frame above the columns has two heights, and `Chrome` is what every measurement takes.** `Chrome::campaign` is an `Option<FrameSize>`, not a bool: `None` for a tab showing the whole board, and `Collapsed` or `Expanded` for one filtered to a campaign, because both heights have to be measured the same way by everything that measures the board. `frame_rows` grew a row, so the two bools that decide the geometry became one `Chrome`, copied from `Board::chrome`: adjacent same-typed parameters are what the Rust Style rule warns about, and the draw and `follow_selection` have to measure one answer or a keypress scrolls against a board the next frame does not draw. The row indices are named (`TAB_ROW`, `CAMPAIGN_ROW`, `BOARD_ROW`, `FOOTER_ROW`), since an index written out by hand goes on meaning what it used to
|
||||
- **The frame above the columns has two heights, and `Chrome` is what every measurement takes.** `Chrome::frame` is an `Option<FrameSize>`, not a bool: `None` for a tab showing the whole board, and `Collapsed` or `Expanded` for one filtered to a campaign or a tag, because both heights have to be measured the same way by everything that measures the board. `screen_rows` grew a row, so the two bools that decide the geometry became one `Chrome`, copied from `Board::chrome`: adjacent same-typed parameters are what the Rust Style rule warns about, and the draw and `follow_selection` have to measure one answer or a keypress scrolls against a board the next frame does not draw. The row indices are named (`TAB_ROW`, `FRAME_ROW`, `BOARD_ROW`, `FOOTER_ROW`), since an index written out by hand goes on meaning what it used to. **Nothing in the geometry is named after campaigns**, because the slot is the tag filter's too: `Chrome::frame` says how tall the frame is and never which filter filled it, so a measurement of the board never has to ask
|
||||
- **The whole description is carried off the one read, and the cut is on the view.** `section_prose` replaced `section_opening`, which cut to the opening line at read time: the campaign file is only in hand while the campaigns directory is being read, so what that read has to carry is everything a view might want, and `CampaignRow::summary` takes the one line the picker draws back off it. Two fields, one cut from the other, are two strings free to come from different reads of the same file
|
||||
- **`CAMPAIGN_PROSE_ROWS` is the collapsed height, and it is a constant rather than a height fitted to the description.** Three rows of prose plus a border either side. A frame that grew and shrank with the campaign would resize every column whenever the filter changed, and a reader would look for a card where the previous campaign's description had put it. It does not have to be right for the longest description, because scrolling is what covers the rest — which is also why three was affordable where one row was not
|
||||
- **The expanded height is a share, not a second constant: half of what the frame and the columns divide.** That is the screen less the tab row and the footer, so the split is even between the two of them rather than even against rows neither gets all of. Half rather than most of it for the same reason the frame is not an overlay: the columns below are the campaign's members, and a reader inspecting the campaign has to go on seeing what it is made of. Floored, so the odd row goes to the cards. `Chrome::campaign_rows` takes the height because of this, and `frame_rows` is where it is called, since that is the one place that already has an area to take a share of — which is what keeps `Chrome` itself pure and copyable from `Board::chrome` with no screen to hand
|
||||
- **The share is bounded at both ends, and `COLUMN_MIN_ROWS` is why.** `Constraint::Min(COLUMN_MIN_ROWS)` would take rows back from a frame that asked for too many, silently, and the frame's own measurement would then disagree with what is drawn — the fault `Chrome` exists to prevent. So the share is capped at what leaves the columns those rows, and floored at `CAMPAIGN_ROWS`, since expanding must never shrink the frame. On a board too short to divide, `enter` gives the collapsed height back rather than a height nothing measured. `the_expanded_share_is_bounded_at_both_ends` sweeps every height from 4 to 60, tabbed and not, because one screen that happens to work says nothing about the arithmetic
|
||||
- **`FRAME_PROSE_ROWS` is the collapsed height, and it is a constant rather than a height fitted to the description.** Three rows of prose plus a border either side. A frame that grew and shrank with the campaign would resize every column whenever the filter changed, and a reader would look for a card where the previous campaign's description had put it. It does not have to be right for the longest description, because scrolling is what covers the rest — which is also why three was affordable where one row was not
|
||||
- **The expanded height is a share, not a second constant: half of what the frame and the columns divide.** That is the screen less the tab row and the footer, so the split is even between the two of them rather than even against rows neither gets all of. Half rather than most of it for the same reason the frame is not an overlay: the columns below are the campaign's members, and a reader inspecting the campaign has to go on seeing what it is made of. Floored, so the odd row goes to the cards. `Chrome::frame_rows` takes the height because of this, and `screen_rows` is where it is called, since that is the one place that already has an area to take a share of — which is what keeps `Chrome` itself pure and copyable from `Board::chrome` with no screen to hand
|
||||
- **The share is bounded at both ends, and `COLUMN_MIN_ROWS` is why.** `Constraint::Min(COLUMN_MIN_ROWS)` would take rows back from a frame that asked for too many, silently, and the frame's own measurement would then disagree with what is drawn — the fault `Chrome` exists to prevent. So the share is capped at what leaves the columns those rows, and floored at `FRAME_ROWS`, since expanding must never shrink the frame. On a board too short to divide, `enter` gives the collapsed height back rather than a height nothing measured. `the_expanded_share_is_bounded_at_both_ends` sweeps every height from 4 to 60, tabbed and not, because one screen that happens to work says nothing about the arithmetic
|
||||
- **The frame says the rest of what it has to say on its borders**, the trade the detail overlay makes with its title and its page indicator: `(id) ~codename · Name` on the top one, the standing on the bottom right, and `q board` then the page indicator on the bottom left. Every row spent here is a row of cards
|
||||
- **The frame's page indicator goes on the bottom border beside `q board`, not on the top beside the title.** The title is cut against the border it sits on, so an indicator up there would shorten a long campaign name the moment its description grew past three rows; and the bottom right is the standing's, which is what the frame is *about* where the indicator is only where the reader has got to in it. Dropped before `q board` when the two cannot both fit, since with a campaign selected the footer's last slot names `ctrl-c quit` and the border is the only place that says `q` gives the board back
|
||||
- **`Focus` is the third place the selection can be, and `Tab` is what holds it.** The board had a column and a card and `select_card` clamped at zero; up from the top card now reaches the frame and down returns to the column it left, since the column index is never what changed. Per tab beside the filter and the offset, so switching away and back returns to where the tab was left. `Focus::Frame` while no campaign is selected is the one state that must never exist — `select_campaign` and `reload` are what keep it from arising
|
||||
- **The frame slot is shared between the two filters, not doubled.** One filter is on at a time, per `Filter`, so a tag frame is the campaign frame with its three slots filled differently: `#tag` in `tag_color` on the top border where the campaign's identity goes, how many tickets carry it on the bottom right where the standing goes, and the annotation in the prose rows. `FrameContent` is what the two are told apart into, and **`frame_content` is the one place they are told apart at all** — the borders, the colour, `q board`, the page indicator, the scroll and the focus are all the campaign frame's, and a second `match` on the filter below that is how the two frames come to behave differently in a way nobody decided
|
||||
- **A tag frame draws the annotation, which is the payoff for declaring a tag.** Whoever is browsing a tag is deciding whether the next ticket belongs in it, and the sentence saying when the tag is appropriate is then on the screen at that moment rather than in `tags.md`, which they would have to know to open. An undeclared tag draws `NO_ANNOTATION` in grey, which is also the frame saying the word was never agreed on — the vocabulary file's own placeholder rather than the description section's, so the frame and the file say the same thing about the same tag. A tag declared with nothing said about it draws the same, since here the two have the same nothing to show; the picker's sections are where the difference is actionable
|
||||
- **A tag has no id, so `y` on its frame copies the word.** A tag *is* its name, matched whole by `ls --tag`, so there are no seven characters to shorten and the `#` the border draws is not part of it — `--tag "#bug"` matches nothing. The footer says `y copy tag` there for the same reason: naming it an id would send the reader looking for a short id on a border that prints a word
|
||||
- **The count on a tag frame is every column's, drawn or not**, the rule the standing holds. With the filter on, those columns *are* the tickets carrying the tag, so it counts what is below it without counting it a second way. The noun is spelled out and pluralised, because a bare number on a border says nothing about what was counted, and there is no derived state beside it: a tag is a word and not a piece of work, so there is no `[open]` to be in
|
||||
- **The frame's page indicator goes on the bottom border beside `q board`, not on the top beside the title.** The title is cut against the border it sits on, so an indicator up there would shorten a long campaign name the moment its description grew past three rows; and the bottom right is the standing's, which is what the frame is *about* where the indicator is only where the reader has got to in it. Dropped before `q board` when the two cannot both fit, since with either filter on the footer's last slot names `ctrl-c quit` and the border is the only place that says `q` gives the board back
|
||||
- **`Focus` is the third place the selection can be, and `Tab` is what holds it.** The board had a column and a card and `select_card` clamped at zero; up from the top card now reaches the frame and down returns to the column it left, since the column index is never what changed. Per tab beside the filter and the offset, so switching away and back returns to where the tab was left. `Focus::Frame` while no filter is on is the one state that must never exist — `select_filter` and `reload` are what keep it from arising, off `Filter::is_whole` rather than off which filter it is, since either draws a frame to hold it
|
||||
- **`Tab::selected` hands back nothing while the frame holds the selection.** Every key that acts on a card has to answer for the frame. `←→` are inert, because the frame spans the width of the board and moving the column underneath would change nothing on screen. `y` is the exception that earns its place: it copies the campaign's short id, so `y copy id` means the id of the selected thing in every state the selection can be in. No card is drawn reversed there either, since that highlight is what says which ticket a key is about
|
||||
- **`enter` routes on the focus through `Board::toggle_focused`: the frame's height on the frame, the overlay on a card.** It used to be inert on the frame for free, because `Tab::selected` hands back nothing and `toggle_detail` therefore had nothing to open. That is no longer an answer, and the routing is in `Board` rather than in the `main.rs` arm for the reason `dismiss` and `scroll_page` are
|
||||
- **`q` does not gain a layer for the expanded frame, and up and down do not take it back.** The expanded frame is the frame at its other height, not a thing laid over the board, so `q` goes on taking the campaign filter off from either height and `enter` is the only key that undoes what `enter` did. The height outlives the selection for the same reason: it is a view of the campaign the reader chose, so the columns stay short with the selection on a card. `Tab::expanded` sits beside the filter and resets where `select_campaign` and `reload` reset the focus and the offset — a different campaign opens collapsed and at the top of its own description
|
||||
- **The toggle re-clamps the frame offset, through `scroll_frame(0, screen)`.** A taller viewport has a smaller last offset than a shorter one, so where the reader was can end up past the end of the frame they just asked for. The draw clamps on its own geometry either way, but the stored value has to be clamped too or the next `pgup` counts down from a number the frame never showed. A scroll of no pages is that clamp and nothing else, which keeps it in the one place it lives
|
||||
- **The frame is out of reach from under an open ticket.** With the overlay open, up and down step through the tickets and it follows, so a selection that reached the frame would have to either close it on an arrow key or leave it showing a ticket nothing is selecting. `an_open_ticket_keeps_the_scroll_keys_from_the_frame` builds that state by hand for exactly this reason: the precedence has to hold whether or not a keypress can reach it
|
||||
- **The standing comes from the columns, not from a walk of the tree.** While a campaign is selected the columns *are* its members, done included, so `Tab::standing` counts what is already in hand rather than paying what `campaign ls` pays per campaign. Counted over every column, drawn or not: hiding done is a change to what is drawn and never to what is counted
|
||||
- **The way out is on the frame's own border, not in the footer.** `q board` sits on the thing it takes away, and the footer row was already at its width naming eight keys. Dropped whole when it and the standing would meet, the rule the page indicator follows
|
||||
- **`c` is named in the footer only on a closed board with nothing selected**, which is where a reader has to find it. Over an open ticket and on a filtered board it is left out: the frame's border then says how to put the campaign away, and the row has no cells to spare. Incomplete rather than wrong, which is the trade this row is allowed to make — what it must never do is name a key by what it used to do
|
||||
- **The footer has three states, because the selection has three places to be.** An open ticket, the frame, and the cards. On the frame it names `↓ board`, `enter expand` or `enter collapse`, the two scroll keys and `y copy id`, and leaves out `←→` because they do nothing there. It has to say which way `enter` goes, since the key is a toggle and the frame is always at one of its two heights. `↑ frame` is not named on the board, on the same trade `c` is dropped on: the frame is drawn directly above the columns and up is the key that reaches it. Nor is the way to collapse an expanded frame named from the cards, which is the same trade again — the frame is right there and `↑` reaches it
|
||||
- **The way out is on the frame's own border, not in the footer.** `q board` sits on the thing it takes away, and the footer row was already at its width naming eight keys. Dropped whole when it and the standing would meet, the rule the page indicator follows, and measured over its spans rather than one string since it is a key hint like any other. Drawn through `key_hint` and not as grey chrome: it is the one key on the board named anywhere but the footer, and a reader who has learnt to look for the cyan letter should not need a second convention to find it. The indicator beside it stays grey, having no key in it
|
||||
- **`c` and `t` are named in the footer only on a closed board with nothing filtered**, which is where a reader has to find them. Over an open ticket and on a filtered board they are left out: the frame's border then says how to put the filter away, and the row has no cells to spare. The tag used to be drawn on that row in its own colour, for want of a frame to draw it in, and 2a83bd4 took that away rather than saying it twice. Incomplete rather than wrong, which is the trade this row is allowed to make — what it must never do is name a key by what it used to do
|
||||
- **The footer has three states, because the selection has three places to be.** An open ticket, the frame, and the cards. On the frame it names `↓ board`, `↵ expand` or `↵ collapse`, the two scroll keys and `y copy id` — `y copy tag` on a tag frame — and leaves out `←→` because they do nothing there. It has to say which way `↵` goes, since the key is a toggle and the frame is always at one of its two heights. `↑ frame` is not named on the board, on the same trade `c` is dropped on: the frame is drawn directly above the columns and up is the key that reaches it. Nor is the way to collapse an expanded frame named from the cards, which is the same trade again — the frame is right there and `↑` reaches it
|
||||
- **`picker: Option<Picker>` is the whole mode**, the shape `search` and `detail` use, and `Board::picker_key` runs beside `search_key` ahead of the action arms for the same reason: an open list owns the keyboard, so `d` must not toggle done and `q` must not quit while a campaign is being chosen. `ctrl-c` is the one key it declines and every other control combination is swallowed, or `ctrl-d` would reach the arm bound to `d`
|
||||
- **The picker's rows are `Tab::campaigns`, not a copy taken when it opened**, so a campaign filed elsewhere appears in an open picker on the next tick. It opens on the campaign already selected, so `c` on a filtered board says where you are as well as offering somewhere to go, and a board with no campaigns gets a `Notice` rather than an empty box that has to be dismissed to learn it was empty
|
||||
- **A picker row draws a real codename only.** The row opens with the short id, so the card's `~<id>` fallback would print it twice and say nothing the second time
|
||||
@@ -317,7 +336,7 @@ and this file is for what someone changing worklane's own code needs.
|
||||
- Id and title only, per 3b16540, both lowercased. The title has to be case insensitive to be worth typing, and giving the id the same treatment lets a pasted id match whatever case it was copied in. An empty or all-space query matches **nothing** rather than everything
|
||||
- **The jump goes through `select_at`, the tail `select_card` already used.** `follow_selection` scrolls the column the card is in, and the offsets are per column and on the `Tab`, so a jump across columns moves the right one; `refresh_detail` keeps an open overlay on the ticket the selection names. A second version of either is how a jump comes to scroll differently from the arrow keys
|
||||
- **A hit closes the prompt and a miss keeps it open**, marked, with the selection untouched. The query can then be corrected in place instead of retyped from `/`. Doing nothing visible is what makes a reader retype a query that was already right
|
||||
- **The prompt takes the whole footer row**, because the key list it replaces describes nothing that currently works while every key is going into the buffer. The typed query is drawn in the default foreground and the keys in grey: one is content, the other is chrome. `no match` is brightred beside the query it is about, since grey chrome is what a reader skips
|
||||
- **The prompt takes the whole footer row**, because the key list it replaces describes nothing that currently works while every key is going into the buffer. Its two keys are drawn as every other key is, cyan on the key and the default foreground on the word. That the query then sits in the same foreground as the descriptions is what the house style costs on this row, and the cursor is what says which half is an input — which it does in a terminal with no colour at all. `no match` stays brightred beside the query it is about, being the one thing on the row that is neither a key nor what was typed
|
||||
- **The real terminal cursor goes after the query**, not a glyph standing in for one. ratatui shows the cursor only for a frame that asked for it, so `set_cursor_position` is also what says "you are typing" while the query is still empty. Clamped to the row, so a query longer than the terminal leaves it on the last cell
|
||||
- Both closed footers name `/`, since the jump works with a ticket open as well: it moves the selection and the overlay follows
|
||||
- Out of scope on purpose, each its own ticket once the input mode exists: `n` and `N` for the next and previous match, searching the description, tags or owner, regex, and filtering the board down to matches rather than selecting one
|
||||
@@ -338,7 +357,11 @@ and this file is for what someone changing worklane's own code needs.
|
||||
|
||||
### The Relations Block
|
||||
- **One builder, two painters.** `relation_rows` decides which edges there are, what they are called and which direction comes first; `relation_cells` decides the layout, the mark and the colours; `paint_cells` turns cells into escapes for the CLI and `span_of` turns the same cells into ratatui spans for the board. Two builders producing one block in two shapes is a pair free to disagree about ordering or padding, which is what this shape exists to prevent
|
||||
- **`Cell` is the unit both renderers take**: a run of text and the colour it is drawn in, `None` for the default foreground. The same trick as the palette itself, where `Color::ansi()` and `From<Color> for ratatui::style::Color` keep one colour from existing for one renderer and not the other
|
||||
- **`Cell` is the unit both renderers take**: a run of text, the colour it is drawn in and the modifier it carries, `None` for the default foreground and for text drawn as it stands. The same trick as the palette itself, where `Color::ansi()` and `From<Color> for ratatui::style::Color` keep one colour from existing for one renderer and not the other, and `Modifier` is that trick a second time for the styles that are not colours
|
||||
- **`Modifier` is the first style on a cell that is not a colour**, and it is an enum with one variant for the reason the palette is one: `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 is not in it, because bold rides inside `Color::Magenta.ansi()` and `span_from` adds it back from the colour alone; a second modifier goes here beside the strike. It is independent of the colour, so a struck run keeps whatever colour its column already gave it
|
||||
- **`Cell::struck` is a builder, not a third constructor.** The strike is decided a whole row at a time and the cells of that row are built by the layout that already chose their colours, so `relation_cells` maps it over the row it has just finished rather than threading the decision through every cell it makes
|
||||
- **`RESET` is a constant both writers share.** `paint` opens a colour and `paint_cell` may open a modifier ahead of one, and a reset that only knew about the colour would leave the strike running to the end of the line
|
||||
- **`Body::push_cell` merges on the whole style, not 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
|
||||
- **`reference_cells` is the one spelling of a cross reference.** The relations block and the Campaign field both go through it, so a dangling reference reads the same way wherever it is shown. There was a `reference_cell` beside it that painted the cells for the CLI; once the whole body became cells the Campaign field stopped needing a string and it was the last caller, so it is gone
|
||||
- **A row carries two marks, kind then status**: what sort of edge this is, then how far the ticket at the other end has got. `blocked by × ◐ (6ce2c47) Title`. Two questions are asked of this block and one glyph could not answer both: which rows hold this ticket up, and whether the ones that do are finished
|
||||
- The status went through one bad shape first. It was a rising bar, `▁▄▆█`, as the only mark, which read as an undifferentiated column of blocks and left the kind to five long words that blur when a ticket carries several. Then the kind took the column alone and the status was lost. Both, in that order, is the answer
|
||||
@@ -379,7 +402,7 @@ and this file is for what someone changing worklane's own code needs.
|
||||
- `Card` wraps a `TicketItem` with the project it came from, `Some` only on the merge tab. Decided at reload rather than passed down to `card_lines` as a "which tab is this" flag. `TicketItem` is therefore `Clone`: the merge holds a second copy rather than re-reading every tree
|
||||
- **The project follows the id, on the card and on the overlay border.** Across boards the id is not an address: two projects can hold the same title, and seven characters do not say where they live. `project_label` takes what the row has left after the mark and the id and ends in an ellipsis, and it is measured before the due date, so on the merge the project wins the narrow column and the date is what `corner_line` drops
|
||||
- `tab` and `shift+tab` cycle rather than clamp, unlike the cards and columns: a row of tabs is a ring, and there is no end of a list to run off. Both were free of every other binding — the columns took `hjkl` and the arrows
|
||||
- **The tab row is drawn only when there is more than one board**, so a single board is the view it has always been. `frame_rows()` gives it `Length(0)` otherwise, which keeps the row indices the same for both cases and is shared with `card_width` and `column_text_height` for the reason `column_areas` is: geometry reproduced by hand drifts from the draw
|
||||
- **The tab row is drawn only when there is more than one board**, so a single board is the view it has always been. `screen_rows()` gives it `Length(0)` otherwise, which keeps the row indices the same for both cases and is shared with `card_width` and `column_text_height` for the reason `column_areas` is: geometry reproduced by hand drifts from the draw
|
||||
- `digest_of` hashes each board's `digest` into one value, so a change in any of them redraws. Do not watch only the first
|
||||
|
||||
### Who Wrote an Entry
|
||||
@@ -457,8 +480,11 @@ and this file is for what someone changing worklane's own code needs.
|
||||
- Priority ramp → brightred (1), red (2), orange (3), cyan (4), grey (5). Green is deliberately absent: it means title
|
||||
- Relation kind mark → brightred `×` blocked by and blocks, cyan `→` relates to, orange `←` regression of and regressed by. A small ramp inside one column, the way the priority meter is: the mark says which kind of edge the row is, so none of these three is a colour standing in for the uuid or the title beside it. Brightred on the cross rather than red, because the id one cell to its right is red and the two would blend. It is the colour and the glyph a held-up card already carries, which is the point: one vocabulary for blocking
|
||||
- Relation status mark → grey `○` backlog, orange `◐` committed, cyan `◐` reviewing, green `●` done, grey `●` discarded, grey `?` for a target the board does not hold. Discarded takes the full circle of done in the grey of the untouched pile: nothing is left to do, and it is not an achievement. The *pair* is what has to be unique, which is the same bargain the two half circles already take, and `every_status_has_a_mark` pins it against `status_dirs`. The second ramp in that column: the shape says how far the target has got and the colour tells the two middle stages apart, since both are half circles. **Green is here and deliberately absent from the priority ramp**, where it would sit on a whole line and read as a title; on a one-cell mark with no title behind it, it is the obvious colour for finished and nothing else wants it. Orange keeps the meaning it already has, Status, and grey keeps unset for the one row with no status to show
|
||||
- **Relation row to a discarded target → struck through, the whole row.** The one thing in the palette that is not a colour, and it is here because the status mark cannot carry it: that mark is one cell in a column of five states, so a row pointing at abandoned work reads as a live dependency, which is exactly what it is not. The strike says the relation no longer stands for anything while the row stays on the ticket, for completeness and for the case the target is moved back out of discarded. Only discarded: a done target still stands for the fact that it was a blocker, and a `_missing_` one says something different again, that the row cannot be resolved at all. Gutter and padding included, so the line runs unbroken from the label to the end of the title, and every cell opens its own SGR 9 since each is closed by its own `RESET`
|
||||
- **The strike is under the colour flag, like every other escape.** A piped `show` carries none of it, the same bargain committed and reviewing already take for being told apart by colour alone, and the board draws it as a style instead. Do not answer the pipe by changing the glyph in the mark column: the pair there has to stay unique, and `every_status_has_a_mark` is what says so
|
||||
- Markdown link → cyan, markers and url kept. Not a new meaning for the colour: the plan numbers, the criterion numbers and the `relates to` mark are already cyan inside a rendered body, and a link is the same kind of thing, a pointer the reader may follow rather than a value. The url is not hidden behind the text the way a renderer would hide it, because `show` prints to a terminal worklane cannot assume will make it clickable, and a link whose target cannot be read is worse than a long line
|
||||
- Chrome → grey. The footer's key names, a rendered `[ ]`, and the overlay's page indicator. Not a new slot: grey already means "what a reader skips", which is the other half of the unset-value meaning, and none of these is a value. The indicator in orange would read as the title it faces across the overlay, in cyan as a timestamp, and in the priority ramp's colours as a level
|
||||
- Chrome → grey. A rendered `[ ]`, the overlay's page indicator and the frame's. Not a new slot: grey already means "what a reader skips", which is the other half of the unset-value meaning, and none of these is a value. The indicator in orange would read as the title it faces across the overlay, in cyan as a timestamp, and in the priority ramp's colours as a level
|
||||
- **A key name → cyan, and bold; what pressing it does → the default foreground.** The one place the palette spends a colour on something that is not a value: a key is what a reader is hunting for on a row they otherwise skip, and with the key merged into its description the colour is the only thing saying which letter to press. Not a second meaning for the timestamp's cyan in any place the two could be confused — nothing on the footer, the prompt or a border hint holds a value at all — and it is the accent frig draws the same row in, which is the point. Grey stays on the chrome around it: the page indicator, and the row's gaps
|
||||
- Chrome → grey, in the history block too: the kind label at the head of a mechanical row, and the `From` on a comment's author line. Both name their row rather than holding a value, which is what grey already says. The label was orange, which means Status everywhere else, so an `owner` or `tags` label claimed a meaning belonging to the value beside it
|
||||
- **A value in the history block takes the colour it has in the metadata table three lines above.** A status is orange, a tags entry goes through the same `tag_cells` the Tags field does, a campaign codename takes `tag_color` bare the way `Codename` does, and `_Not set_`, `_None_` and `_missing_` are grey. An owner stays plain: a person's name is the one value the palette has no meaning for, and spending a colour on the field that needs it least is how a colour stops meaning anything. The block's job is to be scanned, and it is not worth scanning if it has a palette of its own to learn first
|
||||
- History actor → its name through `tag_color`, the way a campaign codename is. Not a new meaning for a reserved colour but the existing use of the tag slots, a name that groups rows: one writer is one colour in every entry it wrote, so a reader sees who has been working a ticket without reading the same name four times. `claude`, `opencode` and a person each get their own
|
||||
|
||||
Generated
+1
-1
@@ -1503,7 +1503,7 @@ dependencies = [
|
||||
|
||||
[[package]]
|
||||
name = "worklane"
|
||||
version = "0.31.3"
|
||||
version = "0.32.2"
|
||||
dependencies = [
|
||||
"anyhow",
|
||||
"assert_cmd",
|
||||
|
||||
+1
-1
@@ -1,6 +1,6 @@
|
||||
[package]
|
||||
name = "worklane"
|
||||
version = "0.31.3"
|
||||
version = "0.32.2"
|
||||
edition = "2024"
|
||||
|
||||
[dependencies]
|
||||
|
||||
@@ -13,7 +13,7 @@ Worklane is a local Kanban flow for agentic software development.
|
||||
| `worklane mv <id> --status <target> [-f]` | Moves ticket between statuses. Default: forward only, one stage at a time. `-f` bypasses both restrictions. `--status discarded` is exempt and reachable from anywhere, for a ticket that will not be done; leaving `discarded` is a backward move and needs `-f`. Discarding is refused while open tickets are blocked by the ticket, `-f` overrides. Records a `status` entry in the ticket's history, after the move: a refused or no-op move records nothing. `--actor` names the writer of that entry |
|
||||
| `worklane set <ticket>` | Replaces fields with `--title`, `--description`, `--acceptance`, `--plan`, `--tags`, `--due`, `--priority`. At least one required. Changing the title renames the file, keeping the UUID. `--clear <field>` returns a field to unset instead, repeatable, taking `due`, `tags`, `priority`, `description`, `acceptance` or `plan`, and writing back exactly what `add` writes for a field it was never given. No `title`, which addresses the ticket, and no `owner`, which is `chown`'s. Replacing and clearing the same field in one call is refused. `--tags` records a `tags` entry in the ticket's history, with the tags before and after, and it is the only field of this command's that is logged; `--actor` names the writer of that entry |
|
||||
| `worklane append <ticket>` | Adds to a section with `--description`, `--acceptance`, `--plan`. At least one required. The description gains a paragraph; list items go on the end, steps numbered on from the last |
|
||||
| `worklane relate <ticket>` | Records an edge to another ticket with `--blocked-by`, `--regression-of` or `--relates-to`, each repeatable. At least one required. Only the ticket named is written; `show` derives the other end by scanning. `mv` refuses to move a ticket blocked by one that is not done, unless `-f` |
|
||||
| `worklane relate <ticket>` | Records an edge to another ticket with `--blocked-by`, `--regression-of` or `--relates-to`, each repeatable. At least one required. Only the ticket named is written; `show` derives the other end by scanning, and a derived row that reads exactly like a stored one is drawn once. `relates to` on a ticket whose target already stores it reports no change, since it is the same edge; `blocked by` and `regression of` read differently from the far end, so a mutual pair is two rows. `mv` refuses to move a ticket blocked by one that is not done, unless `-f`. `--clear <kind> <target>` takes an edge off instead, repeatable, the kind spelled either way, `blocked-by` or `blocked by`. The target resolves against the edges the ticket holds first, by id prefix, which is the only way to reach one whose ticket has been deleted, then as an ordinary ticket search. An edge the ticket does not hold reports no change; a target naming nothing at all is an error. Recording and clearing the same edge in one call is refused |
|
||||
| `worklane chown <user> <ticket>` | Sets the Owner field, the only command that writes it. Free text, checked against nothing. User first and ticket second, after Unix `chown`. `worklane chown --clear <ticket>` returns the field to unset, taking the ticket in the flag since there is no user to give, and not to the git user `add` falls back to. Records an `owner` entry in the ticket's history, with the owner before and after; `--actor` names who made the change, which is not the same as the user argument |
|
||||
| `worklane check <ticket> [criteria...]` | Ticks acceptance criteria, each by number as shown by `show` or by a substring. Several in one call, or `all` for every one of them. Prompts with the numbered list if none is given, or errors with it when there is no terminal |
|
||||
| `worklane uncheck <ticket> [criteria...]` | Unticks acceptance criteria, addressed the same way |
|
||||
@@ -55,6 +55,7 @@ worklane mv <TAB> the same, then --status <TAB> for the five
|
||||
worklane chown alice <TAB> the ticket, which is the second argument here
|
||||
worklane chown --clear <TAB> the ticket, which the flag carries here
|
||||
worklane relate x --blocked-by <TAB>
|
||||
worklane relate x --clear <TAB> the three kinds, not a ticket: the kind comes first
|
||||
worklane campaign show <TAB> the campaigns, from `campaign ls --ids`
|
||||
worklane assign <TAB> the same, since a campaign comes first here
|
||||
worklane ls --campaign <TAB> and again
|
||||
|
||||
+30
-1
@@ -201,13 +201,38 @@ directory beside them, for a repo that has no board yet.
|
||||
worklane relate 1b78a24 --blocked-by 4179958 # this one waits on that one
|
||||
worklane relate 1b78a24 --regression-of 6d327df # this one broke that one's fix
|
||||
worklane relate 1b78a24 --relates-to 7bfb9fc # neighbours, no dependency
|
||||
worklane relate 1b78a24 --clear blocked-by 4179958 # take that edge off again
|
||||
```
|
||||
|
||||
One flag per kind, and each repeats. The ticket comes first and the flag says what it is
|
||||
to the target, so read the call as a sentence: `relate A --blocked-by B` means A waits
|
||||
on B. **Only one side is stored**, on the ticket you name, and `show` derives the other
|
||||
on B.
|
||||
|
||||
**`--clear` is how an edge comes off, and it names the kind and the target**, because a
|
||||
ticket can hold several relations of one kind and emptying all of them is rarely what is
|
||||
wanted. Repeat the flag for more. The kind is spelled either way, `blocked-by` as the flag
|
||||
records it or `blocked by` as `show` prints it. `set --clear` does not reach relations:
|
||||
`relate` is the only writer of the section, so it owns both directions.
|
||||
|
||||
The target is resolved against the edges the ticket already holds first, by id prefix,
|
||||
and only then as an ordinary ticket search. That order is what lets you clear an edge
|
||||
whose target has been **deleted**, which is the case most likely to need it: `show` draws
|
||||
it as `_missing_` with a `?` mark and `mv` warns about it on every move, and no search of
|
||||
the board can reach a ticket that is gone.
|
||||
|
||||
An edge the ticket does not hold reports no change. A target that names nothing at all is
|
||||
an error rather than a no-op, so a mistyped id does not read as success. Recording and
|
||||
clearing the same edge in one call is refused outright, the way `set` refuses a field it
|
||||
is also replacing, and nothing is written. **Only one side is stored**, on the ticket you name, and `show` derives the other
|
||||
end for the ticket at the far side, so never record both directions.
|
||||
|
||||
`relates to` reads the same from both ends, so recording it on the second ticket is
|
||||
refused as no change: the edge is already there, from the far side. `blocked by` and
|
||||
`regression of` are different: the far end reads as `blocks` and `regressed by`, so two
|
||||
tickets each blocking the other is two facts and the block shows both. A symmetric edge
|
||||
comes off with `--clear` at the end that stores it, since that is the only end holding a
|
||||
line to remove.
|
||||
|
||||
`--blocked-by` is enforced: `mv` refuses to move a ticket while a ticket it is blocked by
|
||||
is not in `done` or `discarded`, whichever move it is, and names every open blocker. `-f`
|
||||
moves it anyway, beside the backward and skipping moves it already allows. It is enforced
|
||||
@@ -231,6 +256,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,
|
||||
|
||||
+30
-1
@@ -852,12 +852,17 @@ pub struct AppendArgs {
|
||||
/// Each flag repeats, so several relations of one kind land in a single call. The
|
||||
/// targets are ticket searches, resolved by the same three tiers every other ticket
|
||||
/// argument is, and stored as the target's uuid.
|
||||
///
|
||||
/// `--clear` is the other direction, and it is here rather than on `set` for the reason
|
||||
/// Relations is absent from `section_args`: a relation names a target that has to be
|
||||
/// resolved first, so its one writer owns both adding and removing, the way `chown` owns
|
||||
/// both setting an owner and clearing one.
|
||||
#[derive(clap::Args)]
|
||||
#[command(group(
|
||||
clap::ArgGroup::new("relation_kinds")
|
||||
.required(true)
|
||||
.multiple(true)
|
||||
.args(["blocked_by", "regression_of", "relates_to"])
|
||||
.args(["blocked_by", "regression_of", "relates_to", "clear"])
|
||||
))]
|
||||
pub struct RelateArgs {
|
||||
/// Ticket UUID or title
|
||||
@@ -874,6 +879,18 @@ pub struct RelateArgs {
|
||||
/// Ticket this one is merely related to. Symmetric, so it is recorded once
|
||||
#[arg(long, value_parser = non_empty)]
|
||||
pub relates_to: Vec<String>,
|
||||
|
||||
/// Take a relation off: the kind, then the ticket it points at. Repeat the flag
|
||||
///
|
||||
/// Two values rather than one, because a ticket can hold several relations of one
|
||||
/// kind and emptying every `blocked by` on it is not usually what is wanted. That is
|
||||
/// also why this is not `set --clear`, which names a field and empties the whole of
|
||||
/// it: the "value" here is one edge among several, so the target has to be named too.
|
||||
///
|
||||
/// A `Vec<String>` because clap cannot type the two values of one flag apart.
|
||||
/// [`RelateArgs::cleared`] is where the pairs are split and the kind is parsed.
|
||||
#[arg(long, num_args = 2, value_names = ["KIND", "TARGET"], value_parser = non_empty)]
|
||||
pub clear: Vec<String>,
|
||||
}
|
||||
|
||||
impl RelateArgs {
|
||||
@@ -886,6 +903,18 @@ impl RelateArgs {
|
||||
(RelationKind::RelatesTo, &self.relates_to),
|
||||
]
|
||||
}
|
||||
|
||||
/// The relations asked to be taken off, as a kind and the search naming the target.
|
||||
///
|
||||
/// `num_args = 2` is per occurrence, so clap has already refused an odd number of
|
||||
/// values and every chunk is a full pair. A kind that is not one of the three is
|
||||
/// refused here, before the ticket is resolved and long before anything is written.
|
||||
pub fn cleared(&self) -> anyhow::Result<Vec<(RelationKind, &str)>> {
|
||||
self.clear
|
||||
.chunks(2)
|
||||
.map(|pair| Ok((RelationKind::parse_value(&pair[0])?, pair[1].as_str())))
|
||||
.collect()
|
||||
}
|
||||
}
|
||||
|
||||
/// `check` and `uncheck` are separate commands rather than one verb with a flag,
|
||||
|
||||
+55
-13
@@ -22,7 +22,7 @@ use clap::{CommandFactory, ValueEnum};
|
||||
use clap_complete::Shell;
|
||||
|
||||
use crate::install::SKILLS;
|
||||
use crate::util::Status;
|
||||
use crate::util::{RelationKind, Status};
|
||||
|
||||
/// Subcommands whose first positional is a ticket.
|
||||
///
|
||||
@@ -98,6 +98,11 @@ fn fish_dynamic() -> String {
|
||||
let ticket_commands = TICKET_COMMANDS.join(" ");
|
||||
let ticket_second_commands = TICKET_SECOND_COMMANDS.join(" ");
|
||||
let ticket_flags = flag_list(&TICKET_FLAGS);
|
||||
let relation_kinds = RelationKind::ALL
|
||||
.iter()
|
||||
.map(|kind| kind.flag())
|
||||
.collect::<Vec<_>>()
|
||||
.join(" ");
|
||||
let campaign_commands = CAMPAIGN_COMMANDS.join(" ");
|
||||
let campaign_nested = CAMPAIGN_NESTED_COMMANDS
|
||||
.iter()
|
||||
@@ -188,6 +193,14 @@ complete -c worklane \
|
||||
complete -c worklane -n '__worklane_command_is relate' {ticket_flags} \
|
||||
-x -a '(worklane ls --ids)'
|
||||
|
||||
# `--clear` is the one flag here whose first value is not a ticket, so it is not in
|
||||
# `TICKET_FLAGS`: it takes the kind and then the target, and offering a board listing where
|
||||
# the kind goes would be offering values it refuses. The kinds come from `RelationKind`
|
||||
# rather than being spelled again. The target gets no rule at all, deliberately: fish
|
||||
# completes the value after the flag, and the case this flag exists for is a target whose
|
||||
# ticket is gone, which no listing of the board can offer.
|
||||
complete -c worklane -n '__worklane_command_is relate' -l clear -x -a '{relation_kinds}'
|
||||
|
||||
# Campaigns, from `campaign ls --ids`, in the three places one is named: `assign`'s first
|
||||
# argument, `campaign show`'s only one, and `ls --campaign`.
|
||||
complete -c worklane \
|
||||
@@ -464,22 +477,51 @@ mod tests {
|
||||
}
|
||||
}
|
||||
|
||||
/// `chown --clear` takes a ticket, so it is completed like one, and only under
|
||||
/// `chown`: `set --clear` is the same flag name carrying a field.
|
||||
/// Three commands carry a `--clear` and each one takes something different: `chown`
|
||||
/// takes the ticket, `relate` takes the kind and then the target, and `set` takes a
|
||||
/// field name clap already offers. So each rule is scoped to its own command, and a
|
||||
/// bare search for `-l clear` cannot tell them apart, which is what this used to do.
|
||||
#[test]
|
||||
fn chowns_clear_is_completed_with_tickets_and_sets_is_not() {
|
||||
fn each_clear_flag_is_completed_for_its_own_command() {
|
||||
let script = fish_dynamic();
|
||||
let rule = script
|
||||
.lines()
|
||||
.find(|line| line.starts_with("complete") && line.contains("-l clear"))
|
||||
.expect("chown --clear has a rule of its own");
|
||||
assert!(rule.contains("__worklane_command_is chown"), "{rule}");
|
||||
assert!(rule.contains("worklane ls --ids"), "{rule}");
|
||||
let chown = command().find_subcommand("chown").expect("chown exists").clone();
|
||||
let cli = command();
|
||||
|
||||
let rule_for = |name: &str| {
|
||||
let scope = format!("__worklane_command_is {name}");
|
||||
script
|
||||
.lines()
|
||||
.find(|line| {
|
||||
line.starts_with("complete")
|
||||
&& line.contains("-l clear")
|
||||
&& line.contains(&scope)
|
||||
})
|
||||
.unwrap_or_else(|| panic!("no --clear rule for {name}:\n{script}"))
|
||||
};
|
||||
|
||||
let has_clear = |name: &str| {
|
||||
cli.find_subcommand(name)
|
||||
.unwrap_or_else(|| panic!("no such subcommand: {name}"))
|
||||
.get_arguments()
|
||||
.any(|arg| arg.get_long() == Some("clear"))
|
||||
};
|
||||
|
||||
// `chown --clear` names the ticket in the flag, so the flag completes tickets.
|
||||
assert!(has_clear("chown"), "`chown` has no --clear for the rule to complete");
|
||||
assert!(rule_for("chown").contains("worklane ls --ids"), "{}", rule_for("chown"));
|
||||
|
||||
// `relate --clear` takes the kind first, so it offers the kinds and not a board
|
||||
// listing: tickets there would be candidates the flag refuses. The target, the
|
||||
// second value, is deliberately left uncompleted.
|
||||
assert!(has_clear("relate"), "`relate` has no --clear for the rule to complete");
|
||||
let relate = rule_for("relate");
|
||||
for kind in RelationKind::ALL {
|
||||
assert!(relate.contains(kind.flag()), "{kind:?} is not offered: {relate}");
|
||||
}
|
||||
assert!(
|
||||
chown.get_arguments().any(|arg| arg.get_long() == Some("clear")),
|
||||
"`chown` has no --clear for the rule to complete"
|
||||
!relate.contains("worklane ls --ids"),
|
||||
"tickets offered where the kind goes: {relate}"
|
||||
);
|
||||
|
||||
assert!(
|
||||
!TICKET_FLAGS.contains(&"clear"),
|
||||
"--clear in TICKET_FLAGS would offer tickets to `set --clear`, which takes a field"
|
||||
|
||||
+159
-8
@@ -1105,16 +1105,97 @@ pub fn cmd_append(args: &AppendArgs, start: &Path) -> Result<()> {
|
||||
/// The kinds are a flag each rather than a `--kind` value, so an unknown kind is a
|
||||
/// usage error at the door instead of a line written into the file and refused on the
|
||||
/// way back out.
|
||||
/// The stored relation a `--clear` names, or `None` when the ticket does not hold it.
|
||||
///
|
||||
/// Two tiers, in this order. A uuid prefix against the targets this ticket already
|
||||
/// stores, which is the only tier that can reach a dangling edge: the target's ticket is
|
||||
/// gone, so no search of the board resolves it, and that is the case most likely to need
|
||||
/// clearing. Then the ordinary ticket search, so a title or a prefix of a live ticket
|
||||
/// works here the way it does in every other argument.
|
||||
///
|
||||
/// The prefix tier is the ticket's own relations and not the board, so it stays cheap and
|
||||
/// cannot be made ambiguous by a ticket somewhere else. `MIN_ID_SEARCH` is the same floor
|
||||
/// `resolve_in` puts under its id tier, and the comparison is case insensitive for the
|
||||
/// same reason: an id typed back off a listing has to resolve in whatever case it was
|
||||
/// read.
|
||||
///
|
||||
/// A search that reaches neither tier is an error, not a no-op. A relation the ticket does
|
||||
/// not hold reports no change, which is what the caller asked for either way, but a search
|
||||
/// naming nothing at all is a typo and reporting no change for it would swallow it.
|
||||
fn find_relation(
|
||||
existing: &[Relation],
|
||||
kind: RelationKind,
|
||||
search: &str,
|
||||
title: &str,
|
||||
worklane_dir: &Path,
|
||||
) -> Result<Option<Relation>> {
|
||||
let held: Vec<&Relation> = existing.iter().filter(|held| held.kind == kind).collect();
|
||||
let wanted = search.to_lowercase();
|
||||
|
||||
let by_prefix: Vec<&Relation> = held
|
||||
.iter()
|
||||
.copied()
|
||||
.filter(|held| {
|
||||
search.chars().count() >= MIN_ID_SEARCH
|
||||
&& held.target.to_lowercase().starts_with(&wanted)
|
||||
})
|
||||
.collect();
|
||||
|
||||
match by_prefix.as_slice() {
|
||||
[only] => return Ok(Some((*only).clone())),
|
||||
// Named rather than guessed at, the way an ambiguous ticket search is: the
|
||||
// candidates are printed and nothing is written.
|
||||
[_, _, ..] => {
|
||||
return Err(anyhow!(
|
||||
"'{}' matches {} '{}' relations on '{}': {}. Name more of the id",
|
||||
search,
|
||||
by_prefix.len(),
|
||||
kind.label(),
|
||||
title,
|
||||
by_prefix
|
||||
.iter()
|
||||
.map(|held| short_id(&held.target))
|
||||
.collect::<Vec<_>>()
|
||||
.join(", ")
|
||||
));
|
||||
}
|
||||
[] => {}
|
||||
}
|
||||
|
||||
match resolve_ticket(search, worklane_dir) {
|
||||
Ok((_status, _target_title, target)) => {
|
||||
let target_uuid = parse_ticket_field(&target, "ID");
|
||||
Ok(held.into_iter().find(|held| held.target == target_uuid).cloned())
|
||||
}
|
||||
// The resolver's own reason is carried through, so an ambiguous search says it is
|
||||
// ambiguous rather than being reported as nothing at all.
|
||||
Err(reason) => Err(anyhow!(
|
||||
"No '{}' relation on '{}' matches '{}': {}",
|
||||
kind.label(),
|
||||
title,
|
||||
search,
|
||||
reason
|
||||
)),
|
||||
}
|
||||
}
|
||||
|
||||
pub fn cmd_relate(args: &RelateArgs, start: &Path) -> Result<()> {
|
||||
let worklane_dir = find_worklane_dir(start)?;
|
||||
let (status, title, original) = resolve_ticket(&args.ticket, &worklane_dir)?;
|
||||
let uuid = parse_ticket_field(&original, "ID");
|
||||
let existing = parse_relations(&original, &title)?;
|
||||
|
||||
// Every target resolved and every refusal raised before a byte is written, so a
|
||||
// call naming one good ticket and one bad one records neither.
|
||||
// Every target resolved, every kind parsed and every refusal raised before a byte is
|
||||
// written, so a call naming one good ticket and one bad one records neither.
|
||||
let asked = args.cleared()?;
|
||||
|
||||
let mut items: Vec<String> = Vec::new();
|
||||
let mut changed: Vec<&str> = Vec::new();
|
||||
// Every addition the call asked for, whether or not it is one to write. `items` drops
|
||||
// the ones already held, and a contradiction has to be caught on what was *asked*: a
|
||||
// relation already in the file is not in `items`, so comparing against that would let
|
||||
// `--blocked-by X --clear blocked-by X` quietly remove it.
|
||||
let mut requested: Vec<Relation> = Vec::new();
|
||||
|
||||
for (kind, targets) in args.requested() {
|
||||
for search in targets {
|
||||
@@ -1136,10 +1217,21 @@ pub fn cmd_relate(args: &RelateArgs, start: &Path) -> Result<()> {
|
||||
}
|
||||
|
||||
let relation = Relation { kind, target: target_uuid };
|
||||
requested.push(relation.clone());
|
||||
|
||||
// Already held, either in the file or earlier in this call. Recording it
|
||||
// twice would read as two dependencies on one ticket.
|
||||
if existing.contains(&relation) || items.contains(&relation.item()) {
|
||||
// A symmetric relation the target already stores is already recorded, from
|
||||
// the other end: `show` derives it onto this ticket by scanning, so a line
|
||||
// here would be the same edge stored twice. 4179958 decided `relates to` is
|
||||
// written once and not onto both files, and nothing enforced it until
|
||||
// 03bdc76. Only the symmetric kind, since the target holding
|
||||
// `blocked by <this>` is a cycle rather than a duplicate.
|
||||
let mirrored = kind.is_symmetric()
|
||||
&& parse_relations(&target, &target_title)?
|
||||
.contains(&Relation { kind, target: uuid.clone() });
|
||||
|
||||
// Already held, either in the file, at the far end, or earlier in this call.
|
||||
// Recording it twice would read as two dependencies on one ticket.
|
||||
if existing.contains(&relation) || items.contains(&relation.item()) || mirrored {
|
||||
continue;
|
||||
}
|
||||
|
||||
@@ -1150,15 +1242,74 @@ pub fn cmd_relate(args: &RelateArgs, start: &Path) -> Result<()> {
|
||||
}
|
||||
}
|
||||
|
||||
if items.is_empty() {
|
||||
let mut dropped: Vec<Relation> = Vec::new();
|
||||
let mut cleared: Vec<&str> = Vec::new();
|
||||
|
||||
for (kind, search) in asked {
|
||||
let Some(relation) = find_relation(&existing, kind, search, &title, &worklane_dir)? else {
|
||||
continue;
|
||||
};
|
||||
|
||||
// Both directions in one call, the way `set --clear` refuses a field it is also
|
||||
// replacing: nothing is written rather than one of the two silently winning.
|
||||
if requested.contains(&relation) {
|
||||
return Err(anyhow!(
|
||||
"--{} and --clear {} name the same relation to '{}', so nothing was written",
|
||||
kind.flag(),
|
||||
kind.flag(),
|
||||
short_id(&relation.target)
|
||||
));
|
||||
}
|
||||
|
||||
if dropped.contains(&relation) {
|
||||
continue;
|
||||
}
|
||||
|
||||
dropped.push(relation);
|
||||
if !cleared.contains(&kind.label()) {
|
||||
cleared.push(kind.label());
|
||||
}
|
||||
}
|
||||
|
||||
if items.is_empty() && dropped.is_empty() {
|
||||
report(&[], &title, "Recorded");
|
||||
return Ok(());
|
||||
}
|
||||
|
||||
let content = append_section_body(&ensure_section(&original, &RELATIONS), &RELATIONS, &items)?;
|
||||
// Removals first, by rewriting the section from what is left, then additions appended
|
||||
// to that. Two passes rather than one rebuild of the whole section: a call with no
|
||||
// `--clear` then takes exactly the path it always took, and `append_section_body` goes
|
||||
// on deciding where a new line lands.
|
||||
let mut content = original.clone();
|
||||
|
||||
if !dropped.is_empty() {
|
||||
let kept: Vec<String> = existing
|
||||
.iter()
|
||||
.filter(|held| !dropped.contains(held))
|
||||
.map(|held| held.item())
|
||||
.collect();
|
||||
|
||||
// The placeholder rather than an empty body when the last edge goes, which is the
|
||||
// line `add` writes and the line `append` treats as no content, so the section can
|
||||
// be written to again without it being left above what follows.
|
||||
content = match kept.is_empty() {
|
||||
true => clear_section_body(&content, &RELATIONS)?,
|
||||
false => set_section_body(&content, &RELATIONS, &kept)?,
|
||||
};
|
||||
}
|
||||
|
||||
if !items.is_empty() {
|
||||
content = append_section_body(&ensure_section(&content, &RELATIONS), &RELATIONS, &items)?;
|
||||
}
|
||||
|
||||
save_ticket(&worklane_dir, &status, &uuid, &title, None, &content)?;
|
||||
|
||||
report(&changed, &title, "Recorded");
|
||||
if !changed.is_empty() {
|
||||
report(&changed, &title, "Recorded");
|
||||
}
|
||||
if !cleared.is_empty() {
|
||||
report(&cleared, &title, "Cleared");
|
||||
}
|
||||
Ok(())
|
||||
}
|
||||
|
||||
|
||||
+1119
-277
File diff suppressed because it is too large
Load Diff
+454
-14
@@ -245,13 +245,55 @@ impl From<Color> for ratatui::style::Color {
|
||||
}
|
||||
}
|
||||
|
||||
/// The escape that closes a run, whatever was opened: a colour, a modifier or both.
|
||||
///
|
||||
/// One spelling for the two writers. `paint` opens a colour and `paint_cell` may open a
|
||||
/// modifier ahead of it, and a reset that only knew about the colour would leave the
|
||||
/// strikethrough running to the end of the line.
|
||||
pub const RESET: &str = "\x1b[0m";
|
||||
|
||||
/// A style that is not a colour, which is the other half of what a [`Cell`] carries.
|
||||
///
|
||||
/// An enum with one variant rather than a `bool`, for the reason the palette is an enum:
|
||||
/// the CLI needs an SGR sequence and the board needs a `ratatui` modifier, so a style
|
||||
/// that exists for one renderer and not the other is a compile error. Bold is not here,
|
||||
/// because bold rides inside `Color::Magenta.ansi()` and is added back on the board's
|
||||
/// side from the colour alone; a second modifier would be added here beside this one.
|
||||
#[derive(Debug, Clone, Copy, PartialEq, Eq)]
|
||||
pub enum Modifier {
|
||||
/// What a row about a discarded ticket is drawn with: the relation is still
|
||||
/// recorded, and no longer stands for anything.
|
||||
Strikethrough,
|
||||
}
|
||||
|
||||
impl Modifier {
|
||||
/// The SGR sequence the CLI writes. Closed by [`RESET`], like a colour.
|
||||
pub fn ansi(self) -> &'static str {
|
||||
match self {
|
||||
Modifier::Strikethrough => "\x1b[9m",
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/// The same modifier as ratatui sees it, the other half of [`Modifier::ansi`].
|
||||
///
|
||||
/// SGR 9 and `CROSSED_OUT` are the same request, so the two renderers cannot come to
|
||||
/// draw one struck row and one plain one.
|
||||
impl From<Modifier> for ratatui::style::Modifier {
|
||||
fn from(modifier: Modifier) -> Self {
|
||||
match modifier {
|
||||
Modifier::Strikethrough => ratatui::style::Modifier::CROSSED_OUT,
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/// `color_text` with the decision passed in rather than asked for.
|
||||
///
|
||||
/// The seam matters for anything that aligns columns: a caller has to be able to
|
||||
/// render both ways in one process to prove the padding does not depend on it.
|
||||
pub fn paint(text: &str, color: Color, enabled: bool) -> String {
|
||||
if enabled {
|
||||
format!("{}{}{}", color.ansi(), text, "\x1b[0m")
|
||||
format!("{}{}{}", color.ansi(), text, RESET)
|
||||
} else {
|
||||
text.to_string()
|
||||
}
|
||||
@@ -722,11 +764,15 @@ impl Body {
|
||||
self.push_cell(Cell::plain(c.to_string()));
|
||||
}
|
||||
|
||||
/// One run, merged into the trailing cell when it is the same colour.
|
||||
/// One run, merged into the trailing cell when it is drawn the same way.
|
||||
///
|
||||
/// Merging is not an optimisation. The board draws a span per cell, and the body is
|
||||
/// pushed a character at a time in places, so without this a plain line arrives as
|
||||
/// forty single-character spans for ratatui to wrap.
|
||||
///
|
||||
/// On the whole style and not 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.
|
||||
fn push_cell(&mut self, cell: Cell) {
|
||||
if cell.text.is_empty() {
|
||||
return;
|
||||
@@ -734,7 +780,9 @@ impl Body {
|
||||
|
||||
match self.parts.last_mut() {
|
||||
Some(BodyPart::Cells(cells)) => match cells.last_mut() {
|
||||
Some(last) if last.color == cell.color => last.text.push_str(&cell.text),
|
||||
Some(last) if last.color == cell.color && last.modifier == cell.modifier => {
|
||||
last.text.push_str(&cell.text)
|
||||
}
|
||||
_ => cells.push(cell),
|
||||
},
|
||||
_ => self.parts.push(BodyPart::Cells(vec![cell])),
|
||||
@@ -2075,12 +2123,61 @@ impl RelationKind {
|
||||
}
|
||||
}
|
||||
|
||||
/// Whether the kind reads the same from both ends, which is `relates to` alone.
|
||||
///
|
||||
/// Derived from the two labels rather than listed, so a kind added later answers this
|
||||
/// by construction. A symmetric kind is the only one whose derived row can collide
|
||||
/// with its own stored line: `blocked by` from one end reads as `blocks` from the
|
||||
/// other, and those are two different things to say about one pair of tickets.
|
||||
pub fn is_symmetric(self) -> bool {
|
||||
self.label() == self.inverse_label()
|
||||
}
|
||||
|
||||
/// Every kind, so a caller can walk them without listing them a second time.
|
||||
pub const ALL: [RelationKind; 3] = [
|
||||
RelationKind::BlockedBy,
|
||||
RelationKind::RegressionOf,
|
||||
RelationKind::RelatesTo,
|
||||
];
|
||||
|
||||
/// How the kind is spelled at the command line: the flag that records it, without
|
||||
/// the leading hyphens.
|
||||
///
|
||||
/// A match rather than `label().replace(' ', "-")`, so the pairing is pinned and the
|
||||
/// completion list, the `--clear` value and the flag cannot drift apart.
|
||||
pub fn flag(self) -> &'static str {
|
||||
match self {
|
||||
RelationKind::BlockedBy => "blocked-by",
|
||||
RelationKind::RegressionOf => "regression-of",
|
||||
RelationKind::RelatesTo => "relates-to",
|
||||
}
|
||||
}
|
||||
|
||||
/// One kind from the value `relate --clear` names, or an error listing the three.
|
||||
///
|
||||
/// Both spellings are accepted, the flag's `blocked-by` and the label's `blocked by`,
|
||||
/// because both are in front of the reader: the flag is what recorded the relation and
|
||||
/// the label is what `show` prints in the block and what the file stores. Refusing the
|
||||
/// form the tool itself prints would be a trap for anyone clearing a row they just
|
||||
/// read. Case insensitive, the bargain the id and codename tiers already take.
|
||||
pub fn parse_value(value: &str) -> Result<Self> {
|
||||
let wanted = value.trim().to_lowercase().replace('-', " ");
|
||||
|
||||
RelationKind::ALL
|
||||
.into_iter()
|
||||
.find(|kind| kind.label() == wanted)
|
||||
.ok_or_else(|| {
|
||||
anyhow!(
|
||||
"'{}' is not a relation kind. The kinds are {}",
|
||||
value,
|
||||
RelationKind::ALL
|
||||
.iter()
|
||||
.map(|kind| kind.flag())
|
||||
.collect::<Vec<_>>()
|
||||
.join(", ")
|
||||
)
|
||||
})
|
||||
}
|
||||
}
|
||||
|
||||
/// One stored edge: a kind, and the full uuid of the ticket it points at.
|
||||
@@ -2268,13 +2365,38 @@ pub fn reference_cells(uuid: &str, name: Option<&str>) -> Vec<Cell> {
|
||||
|
||||
/// Cells as the CLI prints them: each one painted, or carried through as it stands.
|
||||
pub fn paint_cells(cells: &[Cell], colored: bool) -> String {
|
||||
cells
|
||||
.iter()
|
||||
.map(|cell| match cell.color {
|
||||
Some(color) => paint(&cell.text, color, colored),
|
||||
None => cell.text.clone(),
|
||||
})
|
||||
.collect()
|
||||
cells.iter().map(|cell| paint_cell(cell, colored)).collect()
|
||||
}
|
||||
|
||||
/// One cell as an escape sequence, its modifier ahead of its colour and one [`RESET`]
|
||||
/// closing both.
|
||||
///
|
||||
/// The modifier is under the same flag the colour is, so a piped `show` and the board's
|
||||
/// own unpainted pass carry no escape at all, per the guideline: a function that takes
|
||||
/// an `enabled` flag has to use it all the way down. The cost is that a pipe cannot see
|
||||
/// a struck row, the same bargain committed and reviewing already take for being told
|
||||
/// apart by colour alone.
|
||||
fn paint_cell(cell: &Cell, colored: bool) -> String {
|
||||
if !colored {
|
||||
return cell.text.clone();
|
||||
}
|
||||
|
||||
// Built rather than matched over the four combinations: either half may be absent,
|
||||
// and a cell with neither has to come back byte for byte as it went in, since the
|
||||
// CLI's output is pinned against what it printed before the cells conversion.
|
||||
let mut opened = String::new();
|
||||
if let Some(modifier) = cell.modifier {
|
||||
opened.push_str(modifier.ansi());
|
||||
}
|
||||
if let Some(color) = cell.color {
|
||||
opened.push_str(color.ansi());
|
||||
}
|
||||
|
||||
if opened.is_empty() {
|
||||
return cell.text.clone();
|
||||
}
|
||||
|
||||
format!("{opened}{}{RESET}", cell.text)
|
||||
}
|
||||
|
||||
/// The mark a blocking relation carries, and a card waiting on one.
|
||||
@@ -2395,19 +2517,39 @@ pub struct RelationTarget {
|
||||
pub struct Cell {
|
||||
pub text: String,
|
||||
pub color: Option<Color>,
|
||||
/// The style that is not the colour, `None` for text drawn as it stands. Kept
|
||||
/// beside the colour rather than folded into it: a struck run keeps whatever colour
|
||||
/// its column already gave it, so the two are independent.
|
||||
pub modifier: Option<Modifier>,
|
||||
}
|
||||
|
||||
impl Cell {
|
||||
pub fn plain(text: impl Into<String>) -> Self {
|
||||
Cell { text: text.into(), color: None }
|
||||
Cell {
|
||||
text: text.into(),
|
||||
color: None,
|
||||
modifier: None,
|
||||
}
|
||||
}
|
||||
|
||||
pub(crate) fn colored(text: impl Into<String>, color: Color) -> Self {
|
||||
Cell {
|
||||
text: text.into(),
|
||||
color: Some(color),
|
||||
modifier: None,
|
||||
}
|
||||
}
|
||||
|
||||
/// The same cell, struck through.
|
||||
///
|
||||
/// A builder rather than a third constructor, because the strike is decided a whole
|
||||
/// row at a time and the cells of that row are built by the layout that already
|
||||
/// chose their colours. `relation_cells` maps this over the row it has just built,
|
||||
/// so nothing has to thread the decision through every cell it makes.
|
||||
pub(crate) fn struck(mut self) -> Self {
|
||||
self.modifier = Some(Modifier::Strikethrough);
|
||||
self
|
||||
}
|
||||
}
|
||||
|
||||
/// The relations of one ticket, both directions, in the order they are shown.
|
||||
@@ -2437,10 +2579,30 @@ pub fn relation_rows(stored: &[Relation], index: &RelationIndex, uuid: &str) ->
|
||||
})
|
||||
.collect();
|
||||
|
||||
// How each stored row reads, which is what a derived row is checked against below.
|
||||
// Collected first because the check cannot borrow `rows` while extending it.
|
||||
let drawn: Vec<(&'static str, String)> =
|
||||
rows.iter().map(|row| (row.label, row.uuid.clone())).collect();
|
||||
|
||||
rows.extend(
|
||||
index
|
||||
.inbound(uuid)
|
||||
// A derived row that reads exactly like a stored one is not a second fact.
|
||||
// Both ends of a symmetric relation can hold a line, since nothing stopped
|
||||
// that until 03bdc76, and the block drew the same neighbour twice under the
|
||||
// same label. The stored row is the one kept: it is the line `--clear` can
|
||||
// address, where the derived one is on a file this ticket does not own.
|
||||
//
|
||||
// Keyed on the label and the target rather than the kind and the target,
|
||||
// which is what keeps a mutual block as two rows: `blocked by` and `blocks`
|
||||
// are different things to say about one pair, and only a symmetric kind,
|
||||
// whose inverse label is its own, can collide with itself.
|
||||
.into_iter()
|
||||
.filter(|(kind, holder)| {
|
||||
!drawn
|
||||
.iter()
|
||||
.any(|(label, target)| *label == kind.inverse_label() && *target == holder.uuid)
|
||||
})
|
||||
.map(|(kind, holder)| RelationRow {
|
||||
kind,
|
||||
label: kind.inverse_label(),
|
||||
@@ -2468,8 +2630,8 @@ pub fn relation_cells(rows: &[RelationRow]) -> Vec<Vec<Cell>> {
|
||||
rows.iter()
|
||||
.map(|row| {
|
||||
let (kind, kind_colour) = relation_mark(row.kind);
|
||||
let (status, status_colour) =
|
||||
status_mark(row.target.as_ref().map(|target| target.status.as_str()));
|
||||
let status_of = row.target.as_ref().map(|target| target.status.as_str());
|
||||
let (status, status_colour) = status_mark(status_of);
|
||||
let padding = " ".repeat(width - row.label.chars().count());
|
||||
|
||||
// Kind, then state, then who: what sort of edge this is, how far the ticket
|
||||
@@ -2489,7 +2651,16 @@ pub fn relation_cells(rows: &[RelationRow]) -> Vec<Vec<Cell>> {
|
||||
row.target.as_ref().map(|target| target.title.as_str()),
|
||||
));
|
||||
|
||||
cells
|
||||
// The whole row, gutter and padding included, so the line runs unbroken from
|
||||
// the label to the end of the title. The strike is what says the target was
|
||||
// discarded, since the status mark cannot: it is one cell in a column of five
|
||||
// states, and a row pointing at abandoned work otherwise reads as a live
|
||||
// dependency, which is exactly what it is not. The relation stays recorded,
|
||||
// for completeness and for the case the target is moved back out.
|
||||
match status_of {
|
||||
Some(DISCARDED) => cells.into_iter().map(Cell::struck).collect(),
|
||||
_ => cells,
|
||||
}
|
||||
})
|
||||
.collect()
|
||||
}
|
||||
@@ -5236,9 +5407,150 @@ Plain line with **bold** and a [link](http://x.test/a).
|
||||
assert_eq!(status_mark(Some("committed")), ("\u{25d0}", Color::Orange));
|
||||
assert_eq!(status_mark(Some("reviewing")), ("\u{25d0}", Color::Cyan));
|
||||
assert_eq!(status_mark(Some("done")), ("\u{25cf}", Color::Green));
|
||||
assert_eq!(status_mark(Some("discarded")), ("\u{25cf}", Color::Grey));
|
||||
assert_eq!(status_mark(None), ("?", Color::Grey));
|
||||
}
|
||||
|
||||
/// The strike is what says the target will never be done, because the status mark
|
||||
/// cannot: it is one cell in a column of five states, and a row pointing at abandoned
|
||||
/// work otherwise reads as a live dependency, which is exactly what it is not.
|
||||
///
|
||||
/// On every cell of the row, gutter and padding included, so the line runs unbroken
|
||||
/// from the label to the end of the title. A cell left out would draw a gap.
|
||||
#[test]
|
||||
fn a_row_pointing_at_a_discarded_target_is_struck_through() {
|
||||
let rows = vec![row(
|
||||
RelationKind::BlockedBy,
|
||||
"blocked by",
|
||||
TARGET,
|
||||
"Dropped",
|
||||
DISCARDED,
|
||||
)];
|
||||
let cells = relation_cells(&rows);
|
||||
|
||||
assert_eq!(cells.len(), 1, "{cells:?}");
|
||||
for cell in &cells[0] {
|
||||
assert_eq!(
|
||||
cell.modifier,
|
||||
Some(Modifier::Strikethrough),
|
||||
"{:?} is not struck, so the line breaks mid row",
|
||||
cell.text
|
||||
);
|
||||
}
|
||||
|
||||
// Every run opened, since a cell is closed by its own reset: the CLI writes one
|
||||
// `\x1b[9m` per cell or the strike stops at the first colour change.
|
||||
let rendered = render_relations(&rows, true);
|
||||
assert_eq!(
|
||||
rendered.matches(Modifier::Strikethrough.ansi()).count(),
|
||||
cells[0].len(),
|
||||
"the CLI did not open the strike on every run:\n{rendered:?}"
|
||||
);
|
||||
}
|
||||
|
||||
/// Only discarded. A row to a live target is drawn as it always was, done included:
|
||||
/// the strike says the relation no longer stands for anything, and a blocker that
|
||||
/// landed still stands for the fact that it was one.
|
||||
///
|
||||
/// Over `status_dirs` rather than the four names, so a status added later is decided
|
||||
/// here rather than inheriting the strike or the plain row by accident.
|
||||
#[test]
|
||||
fn a_row_to_a_live_target_is_not_struck() {
|
||||
let live = status_dirs().into_iter().filter(|status| *status != DISCARDED);
|
||||
|
||||
for status in live {
|
||||
let rows = vec![row(
|
||||
RelationKind::BlockedBy,
|
||||
"blocked by",
|
||||
TARGET,
|
||||
"Alive",
|
||||
status,
|
||||
)];
|
||||
|
||||
for cell in relation_cells(&rows).concat() {
|
||||
assert_eq!(cell.modifier, None, "{status} is struck: {:?}", cell.text);
|
||||
}
|
||||
assert!(
|
||||
!render_relations(&rows, true).contains(Modifier::Strikethrough.ansi()),
|
||||
"{status} is struck through in show"
|
||||
);
|
||||
}
|
||||
}
|
||||
|
||||
/// A target the board no longer holds is not struck either. `?` and `_missing_` say
|
||||
/// the row cannot be resolved, which is a different fact from a target that was
|
||||
/// resolved and abandoned, and striking both would fold the two together.
|
||||
#[test]
|
||||
fn a_row_to_a_missing_target_is_not_struck() {
|
||||
let rows = vec![RelationRow {
|
||||
kind: RelationKind::BlockedBy,
|
||||
label: "blocked by",
|
||||
uuid: TARGET.to_string(),
|
||||
target: None,
|
||||
}];
|
||||
|
||||
for cell in relation_cells(&rows).concat() {
|
||||
assert_eq!(cell.modifier, None, "{:?}", cell.text);
|
||||
}
|
||||
}
|
||||
|
||||
/// Paired the way the guideline demands, and both halves are load bearing. The strike
|
||||
/// is an escape sequence like a colour, so it is under the same flag: a piped `show`
|
||||
/// carries none of it, the same bargain committed and reviewing already take for
|
||||
/// being told apart by colour alone. A renderer that never struck anything would pass
|
||||
/// the absence on its own.
|
||||
#[test]
|
||||
fn the_strike_is_under_the_colour_flag_like_every_other_escape() {
|
||||
let rows = vec![row(
|
||||
RelationKind::BlockedBy,
|
||||
"blocked by",
|
||||
TARGET,
|
||||
"Dropped",
|
||||
DISCARDED,
|
||||
)];
|
||||
|
||||
assert!(
|
||||
render_relations(&rows, true).contains(Modifier::Strikethrough.ansi()),
|
||||
"nothing was struck at all, so the guard below is vacuous"
|
||||
);
|
||||
assert!(
|
||||
!render_relations(&rows, false).contains('\x1b'),
|
||||
"an escape survived the colour being off: {:?}",
|
||||
render_relations(&rows, false)
|
||||
);
|
||||
}
|
||||
|
||||
/// Both halves of the modifier, the way the palette is pinned from both ends. SGR 9
|
||||
/// and `CROSSED_OUT` are the same request, so one renderer cannot come to draw a
|
||||
/// struck row plain while the other strikes it.
|
||||
#[test]
|
||||
fn the_strikethrough_is_the_same_request_in_both_renderers() {
|
||||
assert_eq!(Modifier::Strikethrough.ansi(), "\x1b[9m");
|
||||
assert_eq!(
|
||||
ratatui::style::Modifier::from(Modifier::Strikethrough),
|
||||
ratatui::style::Modifier::CROSSED_OUT
|
||||
);
|
||||
}
|
||||
|
||||
/// The modifier opens ahead of the colour and one reset closes both, which is why the
|
||||
/// reset is a constant the two writers share. A cell carrying neither comes back byte
|
||||
/// for byte as it went in, since the CLI's output is pinned against what it printed
|
||||
/// before the cells conversion.
|
||||
#[test]
|
||||
fn a_cell_opens_its_modifier_ahead_of_its_colour_and_closes_once() {
|
||||
let struck_and_coloured = Cell::colored("x", Color::Red).struck();
|
||||
assert_eq!(
|
||||
paint_cells(&[struck_and_coloured], true),
|
||||
format!("\x1b[9m\x1b[31mx{RESET}")
|
||||
);
|
||||
|
||||
let struck_only = Cell::plain("x").struck();
|
||||
assert_eq!(paint_cells(&[struck_only], true), format!("\x1b[9mx{RESET}"));
|
||||
|
||||
assert_eq!(paint_cells(&[Cell::plain("x")], true), "x");
|
||||
assert_eq!(paint_cells(&[Cell::plain("x").struck()], false), "x");
|
||||
}
|
||||
|
||||
/// Every status the board holds is told apart from the other three. The shape does
|
||||
/// not do it alone, since committed and reviewing are both half circles, so it is the
|
||||
/// pair that has to be unique. Pinned against `status_dirs` rather than the four
|
||||
@@ -5336,6 +5648,134 @@ Plain line with **bold** and a [link](http://x.test/a).
|
||||
assert_eq!(seen.len(), 3, "{seen:?}");
|
||||
}
|
||||
|
||||
/// Every kind is reachable by the flag that records it and by the label `show` prints,
|
||||
/// in any case, and every kind has a flag of its own. Over `RelationKind::ALL` rather
|
||||
/// than the three names, so a kind added later has to be spellable too.
|
||||
#[test]
|
||||
fn a_kind_parses_from_the_flag_spelling_and_the_label_spelling() {
|
||||
let mut flags = std::collections::HashSet::new();
|
||||
|
||||
for kind in RelationKind::ALL {
|
||||
assert!(flags.insert(kind.flag()), "{kind:?} shares its flag with another kind");
|
||||
assert_eq!(kind.flag(), kind.label().replace(' ', "-"), "{kind:?}");
|
||||
|
||||
for spelling in [kind.flag().to_string(), kind.label().to_string()] {
|
||||
for cased in [spelling.to_lowercase(), spelling.to_uppercase()] {
|
||||
assert_eq!(
|
||||
RelationKind::parse_value(&cased).unwrap(),
|
||||
kind,
|
||||
"{cased:?} does not parse as {kind:?}"
|
||||
);
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
/// A value that is not a kind names the three, in the spelling the flags and the
|
||||
/// completions use rather than the spelling the file stores: a reader who has just
|
||||
/// been refused is about to retype the flag.
|
||||
#[test]
|
||||
fn a_value_that_is_not_a_kind_names_the_three() {
|
||||
let refused = RelationKind::parse_value("depends-on").expect_err("accepted");
|
||||
let message = refused.to_string();
|
||||
|
||||
assert!(message.contains("not a relation kind"), "{message}");
|
||||
for kind in RelationKind::ALL {
|
||||
assert!(message.contains(kind.flag()), "{kind:?} is not named: {message}");
|
||||
}
|
||||
}
|
||||
|
||||
/// `relates to` alone reads the same from both ends, and it is derived from the two
|
||||
/// labels rather than listed, so a kind added later answers by construction.
|
||||
#[test]
|
||||
fn only_relates_to_is_symmetric() {
|
||||
for kind in RelationKind::ALL {
|
||||
assert_eq!(
|
||||
kind.is_symmetric(),
|
||||
kind == RelationKind::RelatesTo,
|
||||
"{kind:?} claims symmetry it does not have, or has one it does not claim"
|
||||
);
|
||||
assert_eq!(kind.is_symmetric(), kind.label() == kind.inverse_label(), "{kind:?}");
|
||||
}
|
||||
}
|
||||
|
||||
/// Both ends of a symmetric relation can hold a line, since nothing stopped that
|
||||
/// until 03bdc76, and the block drew the same neighbour twice under the same label.
|
||||
/// The derived row goes and the stored one stays: it is the line `--clear` can
|
||||
/// address, where the derived one lives on a file this ticket does not own.
|
||||
#[test]
|
||||
fn a_derived_row_that_reads_like_a_stored_one_is_drawn_once() {
|
||||
let index = RelationIndex::new(vec![related(
|
||||
TARGET,
|
||||
"The neighbour",
|
||||
"backlog",
|
||||
vec![relation(RelationKind::RelatesTo, SELF)],
|
||||
)]);
|
||||
let stored = vec![relation(RelationKind::RelatesTo, TARGET)];
|
||||
|
||||
let rows = relation_rows(&stored, &index, SELF);
|
||||
assert_eq!(rows.len(), 1, "the same edge is drawn twice: {rows:?}");
|
||||
assert_eq!(rows[0].label, "relates to");
|
||||
assert_eq!(rows[0].uuid, TARGET);
|
||||
|
||||
// The stored one, which is what `--clear` addresses. Both ends carry the same
|
||||
// label here, so the label cannot say which survived: the count is what does.
|
||||
assert_eq!(
|
||||
render_relations(&rows, false),
|
||||
format!("relates to {RELATES_MARK} {} (b1b2c3d) The neighbour\n", smark("backlog"))
|
||||
);
|
||||
}
|
||||
|
||||
/// Only where the row would read the same. A pair of tickets each blocking the other
|
||||
/// is two facts, and the block says both: `blocked by` from this end and `blocks`
|
||||
/// from the other. Deduping on the kind rather than on the label would have folded
|
||||
/// them into one and lost half of what the ticket says.
|
||||
#[test]
|
||||
fn a_mutual_relation_of_an_asymmetric_kind_keeps_both_rows() {
|
||||
for kind in RelationKind::ALL.into_iter().filter(|kind| !kind.is_symmetric()) {
|
||||
let index = RelationIndex::new(vec![related(
|
||||
TARGET,
|
||||
"The other one",
|
||||
"backlog",
|
||||
vec![relation(kind, SELF)],
|
||||
)]);
|
||||
let stored = vec![relation(kind, TARGET)];
|
||||
|
||||
let rows = relation_rows(&stored, &index, SELF);
|
||||
assert_eq!(rows.len(), 2, "{kind:?} lost a row: {rows:?}");
|
||||
assert_eq!(rows[0].label, kind.label(), "{kind:?}");
|
||||
assert_eq!(rows[1].label, kind.inverse_label(), "{kind:?}");
|
||||
}
|
||||
}
|
||||
|
||||
/// The dedupe is per target, not per kind: a second neighbour holding its own
|
||||
/// `relates to` is a different edge and keeps its row.
|
||||
#[test]
|
||||
fn a_second_neighbours_derived_row_survives_the_dedupe() {
|
||||
const OTHER: &str = "cccccccc-1111-4222-8333-444444444444";
|
||||
|
||||
let index = RelationIndex::new(vec![
|
||||
related(
|
||||
TARGET,
|
||||
"The neighbour",
|
||||
"backlog",
|
||||
vec![relation(RelationKind::RelatesTo, SELF)],
|
||||
),
|
||||
related(
|
||||
OTHER,
|
||||
"Another one",
|
||||
"backlog",
|
||||
vec![relation(RelationKind::RelatesTo, SELF)],
|
||||
),
|
||||
]);
|
||||
let stored = vec![relation(RelationKind::RelatesTo, TARGET)];
|
||||
|
||||
let rows = relation_rows(&stored, &index, SELF);
|
||||
assert_eq!(rows.len(), 2, "{rows:?}");
|
||||
assert_eq!(rows[0].uuid, TARGET, "the stored row is not first: {rows:?}");
|
||||
assert_eq!(rows[1].uuid, OTHER, "the other neighbour was dropped: {rows:?}");
|
||||
}
|
||||
|
||||
/// Both directions of one kind carry the same mark, since the kind is what the mark
|
||||
/// says and the label is what says which way it points.
|
||||
#[test]
|
||||
|
||||
@@ -388,3 +388,415 @@ fn a_line_that_is_not_a_relation_is_an_error() {
|
||||
assert!(stderr.contains("is not a relation"), "{stderr}");
|
||||
assert!(stderr.contains("The gated one"), "{stderr}");
|
||||
}
|
||||
|
||||
// --------------------------------------------------------------- clearing --
|
||||
|
||||
/// Two blockers, one taken off by name. The other survives, which is the whole reason
|
||||
/// `--clear` names the target and not just the kind: a ticket can hold several of one
|
||||
/// kind, and emptying all of them is not usually what is wanted.
|
||||
#[test]
|
||||
fn a_relation_is_taken_off_by_its_kind_and_its_target() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
|
||||
run(
|
||||
&temp,
|
||||
&[
|
||||
"relate",
|
||||
GATED,
|
||||
"--blocked-by",
|
||||
BLOCKER,
|
||||
"--blocked-by",
|
||||
FIXED,
|
||||
],
|
||||
);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by", BLOCKER]);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(stdout(&out).contains("Cleared blocked by"), "{}", stdout(&out));
|
||||
|
||||
let content = ticket(&worklane, GATED);
|
||||
assert!(
|
||||
!content.contains(BLOCKER),
|
||||
"the cleared relation is still there: {content}"
|
||||
);
|
||||
assert!(
|
||||
content.contains(&format!("- blocked by {}", FIXED)),
|
||||
"the other one went too: {content}"
|
||||
);
|
||||
}
|
||||
|
||||
/// Both spellings of the kind, because both are in front of the reader: `blocked-by` is
|
||||
/// the flag that recorded it and `blocked by` is what `show` prints and what the file
|
||||
/// stores. Refusing the form the tool itself prints would be a trap.
|
||||
#[test]
|
||||
fn the_kind_takes_the_flag_spelling_and_the_label_spelling() {
|
||||
for kind in ["blocked-by", "blocked by", "Blocked-By"] {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", kind, BLOCKER]);
|
||||
assert!(out.status.success(), "{kind}: {}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(!ticket(&worklane, GATED).contains(BLOCKER), "{kind} did not clear it");
|
||||
}
|
||||
}
|
||||
|
||||
/// The target is a ticket argument like any other, so it resolves by title too.
|
||||
#[test]
|
||||
fn a_cleared_target_resolves_by_title() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by", "blocker"]);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(!ticket(&worklane, GATED).contains(BLOCKER));
|
||||
}
|
||||
|
||||
/// A relation the ticket does not hold is the state the caller asked for, so it reports
|
||||
/// no change rather than failing. The target resolves; the edge is simply not there.
|
||||
#[test]
|
||||
fn clearing_a_relation_the_ticket_does_not_hold_reports_no_change() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
// A kind it does not hold at all, and a target it holds under another kind.
|
||||
for args in [["relates-to", BLOCKER], ["blocked-by", FIXED]] {
|
||||
let out = run(&temp, &["relate", GATED, "--clear", args[0], args[1]]);
|
||||
assert!(out.status.success(), "{args:?}: {}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(stdout(&out).contains("No changes"), "{args:?}: {}", stdout(&out));
|
||||
assert_eq!(ticket(&worklane, GATED), before, "{args:?} wrote something");
|
||||
}
|
||||
}
|
||||
|
||||
/// A search naming nothing at all is a typo, not a state to report. Reporting no change
|
||||
/// for it would swallow it, which is the one thing the no-change rule must not do.
|
||||
#[test]
|
||||
fn clearing_a_target_that_names_nothing_is_an_error() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by", "9999zzzz"]);
|
||||
assert!(!out.status.success(), "{}", stdout(&out));
|
||||
assert_eq!(ticket(&worklane, GATED), before);
|
||||
}
|
||||
|
||||
/// The inverse is derived by a scan rather than stored, so taking the stored line off is
|
||||
/// what takes it off both ends. The other ticket's own file was never touched either way.
|
||||
#[test]
|
||||
fn the_derived_inverse_goes_with_the_stored_line() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
let untouched = ticket(&worklane, BLOCKER);
|
||||
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let shown = stdout(&run(&temp, &["show", BLOCKER]));
|
||||
assert!(shown.contains("blocks"), "the inverse was never derived: {shown}");
|
||||
|
||||
run(&temp, &["relate", GATED, "--clear", "blocked-by", BLOCKER]);
|
||||
let after = stdout(&run(&temp, &["show", BLOCKER]));
|
||||
assert!(!after.contains("blocks"), "the inverse outlived the stored line: {after}");
|
||||
assert_eq!(ticket(&worklane, BLOCKER), untouched, "the other ticket was written to");
|
||||
}
|
||||
|
||||
/// The case most likely to need clearing, and the only one no search of the board can
|
||||
/// reach: the target's ticket is gone, so the prefix tier over the stored targets is what
|
||||
/// finds it. `show` renders it as `_missing_` until it is cleared, and `mv` warns about it
|
||||
/// on every move.
|
||||
#[test]
|
||||
fn a_dangling_relation_can_be_cleared() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
|
||||
fs::remove_file(find(&worklane, BLOCKER)).unwrap();
|
||||
assert!(
|
||||
stdout(&run(&temp, &["show", GATED])).contains("_missing_"),
|
||||
"the fixture is not dangling"
|
||||
);
|
||||
|
||||
// By the short id, which is all a reader has once the title is gone.
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by", &BLOCKER[..7]]);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(!ticket(&worklane, GATED).contains(BLOCKER), "{}", ticket(&worklane, GATED));
|
||||
assert!(!stdout(&run(&temp, &["show", GATED])).contains("_missing_"));
|
||||
}
|
||||
|
||||
/// A prefix short enough to reach two stored targets names the candidates rather than
|
||||
/// guessing, the way an ambiguous ticket search does, and writes nothing.
|
||||
#[test]
|
||||
fn an_ambiguous_prefix_over_the_stored_targets_names_the_candidates() {
|
||||
const ONE: &str = "aaaa1111-0000-4000-8000-000000000000";
|
||||
const TWO: &str = "aaaa2222-0000-4000-8000-000000000000";
|
||||
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
create_ticket(&worklane, "backlog", "Twin one", ONE);
|
||||
create_ticket(&worklane, "backlog", "Twin two", TWO);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", ONE, "--blocked-by", TWO]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by", "aaaa"]);
|
||||
assert!(!out.status.success(), "{}", stdout(&out));
|
||||
|
||||
// The stored-target tier and not the board search, which would find the same two
|
||||
// tickets by their own uuid prefix and report them the same way. The wording is what
|
||||
// tells the two apart, so it is what this asserts.
|
||||
let reason = String::from_utf8_lossy(&out.stderr);
|
||||
assert!(
|
||||
reason.contains("'blocked by' relations on"),
|
||||
"the board answered instead: {reason}"
|
||||
);
|
||||
assert!(reason.contains(&ONE[..7]) && reason.contains(&TWO[..7]), "{reason}");
|
||||
assert_eq!(ticket(&worklane, GATED), before);
|
||||
}
|
||||
|
||||
/// The last edge leaves the placeholder `add` writes, not an empty body, so the section
|
||||
/// can be written to again without the placeholder ending up above what follows it.
|
||||
#[test]
|
||||
fn clearing_the_last_relation_leaves_the_placeholder() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
run(&temp, &["relate", GATED, "--clear", "blocked-by", BLOCKER]);
|
||||
|
||||
let content = ticket(&worklane, GATED);
|
||||
assert!(
|
||||
content.contains(
|
||||
"## Relations
|
||||
_No relations._
|
||||
"
|
||||
),
|
||||
"{content}"
|
||||
);
|
||||
|
||||
// And it is written to again without the placeholder being left behind.
|
||||
run(&temp, &["relate", GATED, "--relates-to", FIXED]);
|
||||
let again = ticket(&worklane, GATED);
|
||||
assert!(again.contains(&format!("- relates to {}", FIXED)), "{again}");
|
||||
assert!(
|
||||
!again.contains("_No relations._"),
|
||||
"the placeholder outlived the edge: {again}"
|
||||
);
|
||||
}
|
||||
|
||||
/// The same file surgery `relate` already does, so the tick, the handwritten section and
|
||||
/// the prose survive a clear the way they survive a record.
|
||||
#[test]
|
||||
fn clearing_leaves_everything_it_was_not_asked_about_alone() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(
|
||||
&temp,
|
||||
&[
|
||||
"relate",
|
||||
GATED,
|
||||
"--blocked-by",
|
||||
BLOCKER,
|
||||
"--relates-to",
|
||||
FIXED,
|
||||
],
|
||||
);
|
||||
run(&temp, &["relate", GATED, "--clear", "blocked-by", BLOCKER]);
|
||||
|
||||
let content = ticket(&worklane, GATED);
|
||||
assert!(content.contains("- [x] Crit one"), "the tick was lost: {content}");
|
||||
assert!(
|
||||
content.contains("## Notes\nA handwritten note the tool knows nothing about.\n"),
|
||||
"the unknown section was lost: {content}"
|
||||
);
|
||||
assert!(content.contains("1. Step one"), "{content}");
|
||||
assert!(content.contains("- **Owner**: alice"), "{content}");
|
||||
assert!(content.contains("- **Status**: backlog"), "{content}");
|
||||
}
|
||||
|
||||
/// One call does both, and each half reports itself in its own words.
|
||||
#[test]
|
||||
fn one_call_records_and_clears_different_relations() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
|
||||
let out = run(
|
||||
&temp,
|
||||
&[
|
||||
"relate",
|
||||
GATED,
|
||||
"--clear",
|
||||
"blocked-by",
|
||||
BLOCKER,
|
||||
"--relates-to",
|
||||
FIXED,
|
||||
],
|
||||
);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
|
||||
let reported = stdout(&out);
|
||||
assert!(reported.contains("Recorded relates to"), "{reported}");
|
||||
assert!(reported.contains("Cleared blocked by"), "{reported}");
|
||||
|
||||
let content = ticket(&worklane, GATED);
|
||||
assert!(!content.contains(BLOCKER), "{content}");
|
||||
assert!(content.contains(&format!("- relates to {}", FIXED)), "{content}");
|
||||
}
|
||||
|
||||
/// Recording and clearing the same relation in one call is refused outright, the way
|
||||
/// `set` refuses a field it is also replacing: nothing is written rather than one of the
|
||||
/// two silently winning.
|
||||
///
|
||||
/// It has to be caught on what the call *asked* for and not on what it would write. A
|
||||
/// relation already in the file is not among the additions, so comparing against those
|
||||
/// would let this call quietly remove one.
|
||||
#[test]
|
||||
fn recording_and_clearing_the_same_relation_is_refused() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(
|
||||
&temp,
|
||||
&[
|
||||
"relate",
|
||||
GATED,
|
||||
"--blocked-by",
|
||||
BLOCKER,
|
||||
"--clear",
|
||||
"blocked-by",
|
||||
BLOCKER,
|
||||
],
|
||||
);
|
||||
assert!(!out.status.success(), "{}", stdout(&out));
|
||||
assert!(
|
||||
String::from_utf8_lossy(&out.stderr).contains("nothing was written"),
|
||||
"{}",
|
||||
String::from_utf8_lossy(&out.stderr)
|
||||
);
|
||||
assert_eq!(ticket(&worklane, GATED), before, "the relation was removed anyway");
|
||||
}
|
||||
|
||||
/// A kind that is not one of the three is refused before the ticket is resolved, so
|
||||
/// nothing is written. Exit 1 rather than clap's 2: the value is one of a pair clap
|
||||
/// cannot type apart, so the kind is parsed by `RelateArgs::cleared`.
|
||||
#[test]
|
||||
fn an_unknown_kind_in_a_clear_is_refused() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "depends-on", BLOCKER]);
|
||||
assert!(!out.status.success(), "{}", stdout(&out));
|
||||
|
||||
let reason = String::from_utf8_lossy(&out.stderr);
|
||||
assert!(reason.contains("not a relation kind"), "{reason}");
|
||||
// The message names the three, in the spelling the flags and the completions use.
|
||||
for kind in ["blocked-by", "regression-of", "relates-to"] {
|
||||
assert!(reason.contains(kind), "{reason}");
|
||||
}
|
||||
assert_eq!(ticket(&worklane, GATED), before);
|
||||
}
|
||||
|
||||
/// `--clear` takes exactly two values per occurrence, so clap refuses an odd number with
|
||||
/// a usage error and nothing reaches the handler.
|
||||
#[test]
|
||||
fn a_clear_with_one_value_is_a_usage_error() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--clear", "blocked-by"]);
|
||||
assert_eq!(out.status.code(), Some(2), "{}", stdout(&out));
|
||||
assert_eq!(ticket(&worklane, GATED), before);
|
||||
}
|
||||
|
||||
/// The far end already stores it, so the edge is already recorded: `show` derives it onto
|
||||
/// this ticket by scanning. A line here would be the same edge on two files, which
|
||||
/// 4179958 decided against and nothing enforced until 03bdc76.
|
||||
#[test]
|
||||
fn a_relates_to_the_target_already_stores_is_not_stored_again() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
|
||||
run(&temp, &["relate", BLOCKER, "--relates-to", GATED]);
|
||||
let before = ticket(&worklane, GATED);
|
||||
|
||||
let out = run(&temp, &["relate", GATED, "--relates-to", BLOCKER]);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(stdout(&out).contains("No changes"), "{}", stdout(&out));
|
||||
assert_eq!(ticket(&worklane, GATED), before, "the mirror was stored anyway");
|
||||
|
||||
// Still shown, since it was recorded at the other end.
|
||||
let shown = stdout(&run(&temp, &["show", GATED]));
|
||||
assert_eq!(shown.matches("relates to").count(), 1, "{shown}");
|
||||
}
|
||||
|
||||
/// A board that already holds both directions draws the edge once. The refusal above
|
||||
/// stops it recurring; this is what repairs a ticket that already has it, without an edit.
|
||||
#[test]
|
||||
fn a_relates_to_stored_at_both_ends_is_drawn_once() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
let worklane = board(&temp);
|
||||
|
||||
// Both lines written directly, which is the state a board recorded before the refusal
|
||||
// is in. The CLI will not produce it any more, so nothing else can set this up.
|
||||
for (holder, target) in [(GATED, BLOCKER), (BLOCKER, GATED)] {
|
||||
let path = find(&worklane, holder);
|
||||
let content = fs::read_to_string(&path).unwrap().replace(
|
||||
"## Metadata",
|
||||
&format!("## Relations\n- relates to {target}\n\n## Metadata"),
|
||||
);
|
||||
fs::write(&path, content).unwrap();
|
||||
}
|
||||
|
||||
let shown = stdout(&run(&temp, &["show", GATED]));
|
||||
assert_eq!(shown.matches("relates to").count(), 1, "the edge is drawn twice:\n{shown}");
|
||||
assert_eq!(shown.matches(&BLOCKER[..7]).count(), 1, "{shown}");
|
||||
|
||||
// And from the other end, which stores its own line and derives this one.
|
||||
let far = stdout(&run(&temp, &["show", BLOCKER]));
|
||||
assert_eq!(far.matches("relates to").count(), 1, "{far}");
|
||||
}
|
||||
|
||||
/// Only where the row reads the same. Two tickets each blocking the other is two facts,
|
||||
/// and the block says both: `blocked by` from this end, `blocks` from the other.
|
||||
#[test]
|
||||
fn a_mutual_block_is_still_drawn_from_both_ends() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
board(&temp);
|
||||
|
||||
run(&temp, &["relate", GATED, "--blocked-by", BLOCKER]);
|
||||
let out = run(&temp, &["relate", BLOCKER, "--blocked-by", GATED]);
|
||||
assert!(out.status.success(), "{}", String::from_utf8_lossy(&out.stderr));
|
||||
assert!(
|
||||
!stdout(&out).contains("No changes"),
|
||||
"the second was refused: {}",
|
||||
stdout(&out)
|
||||
);
|
||||
|
||||
let shown = stdout(&run(&temp, &["show", GATED]));
|
||||
assert!(shown.contains("blocked by"), "{shown}");
|
||||
assert!(shown.contains("blocks"), "the derived direction was dropped:\n{shown}");
|
||||
}
|
||||
|
||||
/// The same for the other asymmetric kind, whose inverse label also differs from its own.
|
||||
#[test]
|
||||
fn a_mutual_regression_is_still_drawn_from_both_ends() {
|
||||
let temp = TempDir::new().unwrap();
|
||||
board(&temp);
|
||||
|
||||
run(&temp, &["relate", GATED, "--regression-of", BLOCKER]);
|
||||
run(&temp, &["relate", BLOCKER, "--regression-of", GATED]);
|
||||
|
||||
let shown = stdout(&run(&temp, &["show", GATED]));
|
||||
assert!(shown.contains("regression of"), "{shown}");
|
||||
assert!(
|
||||
shown.contains("regressed by"),
|
||||
"the derived direction was dropped:\n{shown}"
|
||||
);
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user