Page MenuHomePhabricator

After reloading transactions for the recipient while building transaction mail, put them in the input order
ClosedPublic

Authored by epriestley on May 30 2019, 10:37 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Jun 30, 9:57 AM
Unknown Object (File)
Tue, Jun 30, 12:37 AM
Unknown Object (File)
Jun 25 2026, 9:20 AM
Unknown Object (File)
Jun 19 2026, 5:40 PM
Unknown Object (File)
Jun 4 2026, 2:27 PM
Unknown Object (File)
Apr 2 2026, 2:48 AM
Unknown Object (File)
Jan 15 2026, 9:51 AM
Unknown Object (File)
Jan 9 2026, 7:55 PM
Subscribers
None

Details

Summary

Ref T13303. In D20525 I fixed an issue where transaction rendering could use cached values with the wrong viewer by reloading transactions.

However, reloading transactions may also reorder them as a side effect, since withPHIDs(...) does not imply an order. This can make transaction rendering order in mail wrong/inconsistent.

Instead, reorder the transactions before continuing so mail transaction order is consistent.

Test Plan

Applied a group of transactions to a task, saw a more consistent rendering order in mail after the change.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable