Page MenuHomePhabricator

Use the same transaction group ID for transactions applied indirectly by a sub-editor
ClosedPublic

Authored by epriestley on May 22 2019, 9:41 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Dec 23, 10:45 AM
Unknown Object (File)
Thu, Dec 12, 10:39 PM
Unknown Object (File)
Tue, Dec 10, 12:12 PM
Unknown Object (File)
Wed, Nov 27, 10:59 AM
Unknown Object (File)
Nov 23 2024, 12:43 AM
Unknown Object (File)
Nov 18 2024, 7:37 PM
Unknown Object (File)
Nov 15 2024, 12:48 PM
Unknown Object (File)
Nov 10 2024, 8:56 PM
Subscribers
None

Details

Summary

Ref T13283. Currently, each Editor sets its own group ID, so if you create a revision and then Herald does some stuff, the two groups of transactions get different group IDs.

This means the test console is slightly misleading (it will only pick up the Herald transactions). It's going to be misleading anyway (Herald obviously can't evaluate Herald transactions) but this is at least a little closer to reality and stops Herald actions from masking non-Herald actions.

Test Plan
  • Created a revision. Herald applied one transaction.
  • Used the test console.
  • Before: The test console only picked up the single most recent Herald transaction.
  • After: The test console picked up the whole transaction group.

Screen Shot 2019-05-22 at 2.38.14 PM.png (377×1 px, 77 KB)

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable