(641e3d5) Scope metadata field lookup to the Metadata section, and bump to 0.2.1
parse_ticket_field searched every line of the file with contains, and set_status_field rewrote the first line starting with the Status marker wherever it sat. Tickets in this repo quote field markers in their descriptions, so a description list shaped like metadata was read in place of the real value and rewritten by mv, leaving the metadata stale. Both now scan only the lines under the Metadata heading and match on a line prefix rather than a substring. A file with no Metadata heading has no fields, so mv reports the missing Status field instead of editing prose. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This commit is contained in:
co-authored by
Claude Opus 5
parent
2503f9aee9
commit
ab1dae098c
@@ -51,6 +51,7 @@
|
||||
- Colorization functions (`colorize_line`, `colorize_metadata`, `colorize_ordered`, `content_trim_colored`) handle markdown formatting
|
||||
- `resolve_ticket()` scans all status directories — it's the single source for ticket lookup by UUID prefix, title, or filename
|
||||
- `parse_ticket_field()` handles extracting metadata values from markdown format
|
||||
- Field lookup, read and write, is scoped to the lines under the `## Metadata` heading and anchored to the start of the line. Prose above it is free text: tickets in this repo quote field markers in their descriptions, and an unscoped search reads or rewrites those instead. `set_status_field()` carries the same scoping
|
||||
|
||||
### Ticket Resolution
|
||||
- `resolve_ticket()` returns `(status, title, content)` tuple
|
||||
|
||||
Reference in New Issue
Block a user