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
F19517314: D20563.diff
Thu, Jan 15, 9:51 AM
F19507374: D20563.diff
Fri, Jan 9, 7:55 PM
F19497321: D20563.diff
Thu, Jan 8, 12:07 PM
F19472457: D20563.diff
Wed, Jan 7, 7:43 AM
F18985116: D20563.id.diff
Nov 17 2025, 12:53 PM
F18854726: D20563.diff
Nov 1 2025, 12:29 AM
F18834867: D20563.id.diff
Oct 26 2025, 11:26 AM
F18830748: D20563.diff
Oct 25 2025, 8:32 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
Branch
sort1
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 22929
Build 31458: Run Core Tests
Build 31457: arc lint + arc unit