Page MenuHomePhabricator

Expose Differential actions for "transaction.search" in a basic way
ClosedPublic

Authored by epriestley on Jun 27 2018, 5:02 PM.
Tags
None
Referenced Files
F18910834: D19509.id.diff
Sun, Nov 9, 3:27 AM
F18906367: D19509.diff
Sat, Nov 8, 6:04 PM
F18763956: D19509.id.diff
Oct 7 2025, 3:18 AM
F18762110: D19509.diff
Oct 6 2025, 5:37 PM
F18679451: D19509.id46648.diff
Sep 26 2025, 12:50 AM
F18621532: D19509.id46652.diff
Sep 15 2025, 8:41 AM
F18509686: D19509.id.diff
Sep 5 2025, 3:32 AM
F18502961: D19509.diff
Sep 4 2025, 10:46 PM
Subscribers
None

Details

Summary

See PHI725. Ref T13151. These actions are somewhat unusual and I considered different ways to represent them (make them look like "status" transactions; build multiple synthetic transactions) but ultimately landed on the simplest approach of just exposing them more or less as they exist internally.

I haven't included data for any of them. Most don't really have any data, but "accept" does. I'm holding off on providing more data until after T731, which may shake up the internal format.

Test Plan

Applied most of these transactions against a revision, queried for it with transaction.search, got distinguishable transactions out.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable