aboutsummaryrefslogtreecommitdiff
path: root/docs/issue-representation-spec.org
diff options
context:
space:
mode:
authorCraig Jennings <c@cjennings.net>2026-05-27 16:52:07 -0500
committerCraig Jennings <c@cjennings.net>2026-05-27 16:52:07 -0500
commit34b4e5ecd8468129cb97e870987fc8bb8d27d6e2 (patch)
tree6f6cc33ab635f6f541857ea38b817ad0688a4f25 /docs/issue-representation-spec.org
parent78bd607f8dd1f4c29e4d7dda9744b06bf7352105 (diff)
downloadpearl-34b4e5ecd8468129cb97e870987fc8bb8d27d6e2.tar.gz
pearl-34b4e5ecd8468129cb97e870987fc8bb8d27d6e2.zip
fix(save): detect comment edits with a rendered-Org hash, not the md round-trip
A comment whose markdown doesn't survive md->org->md (a heading, single-asterisk italics) was flagged changed on every save, because the dirty scan compared org-to-md of the rendered body against the stored markdown hash. When the comment was authored by someone else, that surfaced as "1 read-only comment skipped" on every save even though nothing had been edited. Descriptions already dodge this: 9424b84 gave them LINEAR-DESC-ORG-SHA256 and compared Org-to-Org. I did the same for comments. pearl--format-comment now writes LINEAR-COMMENT-ORG-SHA256 (the rendered body hash), and a new pearl--comment-dirty-p compares the current body against it, falling back to the old markdown hash for comments rendered before the baseline existed. Both detection sites use it: the save scan and the edit-current-comment no-op check. The markdown hash stays for the remote-conflict gate.
Diffstat (limited to 'docs/issue-representation-spec.org')
0 files changed, 0 insertions, 0 deletions