aboutsummaryrefslogtreecommitdiffstats
path: root/docs/superpowers/specs
diff options
context:
space:
mode:
authorDanilo M. <danix@danix.xyz>2026-10-31 12:43:21 +0100
committerDanilo M. <danix@danix.xyz>2026-11-17 10:26:29 +0100
commit600a1c787f42ba51a60abf314308f1458163c7a5 (patch)
tree032698c01bb03cfb6258f4fd6c7ba0f38f3a3e15 /docs/superpowers/specs
parent097507f83d3d559455910e7c9e8969abd2eef961 (diff)
downloadqtmaildir-600a1c787f42ba51a60abf314308f1458163c7a5.tar.gz
qtmaildir-600a1c787f42ba51a60abf314308f1458163c7a5.zip
fix: handle every rule answer, and keep its failure out of errorOccurred
A second Apply overwrote the pending token, so the first rule's answer was dropped as stale although its writes had landed: no undo, no pending count, no accounts. A write's answer cannot be superseded, so the token is gone and every ruleApplied() is handled. Pending counts are keyed by generation for the same reason, since a second Apply before the first count returned dropped the first Apply entirely. applyRule() no longer emits errorOccurred(). That path reverted an unrelated in-flight user write and its message was then overwritten by "nothing to change". The failure travels in the reply instead: ruleApplied(description, changes, error). openReadOnly() and writeTags() take an optional error out-parameter so the rule's path stays quiet. The window shows the error, still records and offers undo for whatever landed first, and names the rule from the reply's description. Item 212. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Diffstat (limited to 'docs/superpowers/specs')
0 files changed, 0 insertions, 0 deletions