Page MenuHomePhabricator

When mail (like "!history" mail) has multiple comments, label them separately
ClosedPublic

Authored by epriestley on Apr 16 2018, 2:53 PM.
Tags
None
Referenced Files
F14412660: D19373.diff
Tue, Dec 24, 1:19 PM
Unknown Object (File)
Wed, Dec 11, 3:34 AM
Unknown Object (File)
Sat, Nov 30, 11:03 AM
Unknown Object (File)
Nov 23 2024, 5:59 AM
Unknown Object (File)
Nov 16 2024, 3:32 PM
Unknown Object (File)
Oct 21 2024, 8:59 AM
Unknown Object (File)
Oct 9 2024, 9:24 AM
Unknown Object (File)
Oct 2 2024, 8:48 PM
Subscribers
None

Details

Summary

Depends on D19372. Ref T13124. See PHI505. Currently, if you !history a task with a lot of comments, you get output like this:

alice added a comment.
bailey added a comment.
alice added a comment.
alice added a comment.

AAAA

BBBB

AAAA

AAAA

This is impossible to read. Put the "alice added a comment." headers above the actual comments for comments after the first.

These types of mail messages are unusual, but occur in several cases:

  • The new !history command.
  • Multiple comments on a draft revision before it promotes out of draft.
  • (Probably?) Conduit API updates which submit multiple comment transactions for some reason.
Test Plan

Used bin/mail receive-test to send a !history command to a task, saw a much more readable rendering of the transaction log in the resulting email.

Diff Detail

Repository
rP Phabricator
Branch
history2
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 20155
Build 27347: Run Core Tests
Build 27346: arc lint + arc unit