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
F13052683: D19373.id.diff
Fri, Apr 19, 10:28 AM
Unknown Object (File)
Sun, Mar 31, 11:28 AM
Unknown Object (File)
Mar 10 2024, 11:18 AM
Unknown Object (File)
Feb 3 2024, 6:48 PM
Unknown Object (File)
Jan 25 2024, 3:19 AM
Unknown Object (File)
Dec 22 2023, 6:56 PM
Unknown Object (File)
Dec 21 2023, 11:51 PM
Unknown Object (File)
Nov 30 2023, 12:23 AM
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
Lint
Lint Not Applicable
Unit
Tests Not Applicable