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
F13088316: D20563.id.diff
Thu, Apr 25, 1:23 AM
F13087875: D20563.diff
Thu, Apr 25, 1:09 AM
Unknown Object (File)
Mon, Apr 22, 2:05 AM
Unknown Object (File)
Sat, Apr 20, 3:14 AM
Unknown Object (File)
Wed, Apr 17, 2:43 PM
Unknown Object (File)
Thu, Mar 28, 11:20 PM
Unknown Object (File)
Mar 23 2024, 7:22 AM
Unknown Object (File)
Mar 23 2024, 7:22 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