Skip to content

Keep one resent tag when resending a resend - #34

Merged
jszobody merged 2 commits into
masterfrom
fix/resent-tag-duplicates
Oct 3, 2026
Merged

jszobody merged 2 commits into
masterfrom
fix/resent-tag-duplicates

Conversation

@jszobody

@jszobody jszobody commented Oct 3, 2026

Copy link
Copy Markdown
Member

Fixes #16.

A resend copied every tag from the message it replayed, then added resent. When you resend a resend, the copied tags already include resent, so a chain of resends stored resent, then resent resent, and so on.

The copied tags and resent are now deduplicated together, so every resend stores resent exactly once. The resend chain's depth is still in resent_from_id (resendChain()), so nothing is lost. The dedupe also drops a tag that appeared twice on the original.

Test: a resend of a resend of a message tagged receipt, receipt now stores ['receipt', 'resent']. Before the fix it stored ['receipt', 'receipt', 'resent', 'resent'].

All 453 tests pass, and static analysis is clean.

There's no UI code change; the dashboard's tag badges just stop repeating. #33 (the fix for #31) edits another part of the same file, so the two branches should merge cleanly in either order.

Each resend copied the source's tags, including its "resent" tag,
then added another, so a chain of resends showed "resent resent ...".
Copied tags are now deduplicated; resent_from_id still records depth.

Fixes #16
@jszobody
jszobody merged commit 4edf0a1 into master Oct 3, 2026
1 check passed
@jszobody
jszobody deleted the fix/resent-tag-duplicates branch October 3, 2026 14:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ResentMessage stacks duplicate resent tags when resending a resend

1 participant