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
F18790294: D20563.id.diff
Wed, Oct 15, 1:30 PM
F18749184: D20563.id49054.diff
Sat, Oct 4, 2:45 AM
F18699880: D20563.diff
Sat, Sep 27, 1:52 PM
F18673124: D20563.diff
Thu, Sep 25, 9:24 AM
F18657326: D20563.diff
Sep 23 2025, 1:20 AM
F18597511: D20563.id49056.diff
Sep 13 2025, 3:03 AM
F18570308: D20563.id49056.diff
Sep 10 2025, 3:21 AM
F18570303: D20563.id49054.diff
Sep 10 2025, 3:21 AM
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