Page MenuHomePhabricator

Let Herald activation depend on which transactions are being applied, and generate transactions
ClosedPublic

Authored by epriestley on Mar 5 2014, 3:03 AM.
Tags
None
Referenced Files
Unknown Object (File)
Fri, Dec 20, 6:26 AM
Unknown Object (File)
Fri, Dec 6, 6:29 PM
Unknown Object (File)
Wed, Dec 4, 12:42 PM
Unknown Object (File)
Tue, Dec 3, 8:36 PM
Unknown Object (File)
Wed, Nov 27, 12:27 AM
Unknown Object (File)
Wed, Nov 27, 12:27 AM
Unknown Object (File)
Wed, Nov 27, 12:27 AM
Unknown Object (File)
Wed, Nov 27, 12:27 AM
Subscribers

Details

Summary

Ref T2222. Ref T4484. This is a stepping stone to getting Herald supported in the new Differental code. Generally:

  • Instead of an Editor either supporting or not supporting Herald, let it choose based on transactions. Specifically, Differential only runs rules on revision creation and diff updates.
  • Optionally, allow an Editor to return some transactions to apply instead of having to apply everything itself. This lets us make it clear why changes happend in the transaction log, and share more code.
  • I updated only one transaction type (owners in Maniphest) since it was the easiest and cleanest to update and test. Everything else still works like it used to, it just won't generate a transaction record yet.
  • The transaction records are a touch rough, but we can clean them up later.
Test Plan

{F122282}

Diff Detail

Repository
rP Phabricator
Branch
dxherald1
Lint
Lint Passed
Unit
No Test Coverage

Event Timeline

btrahan edited edge metadata.
btrahan added inline comments.
src/applications/transactions/editor/PhabricatorApplicationTransactionEditor.php
643

nice

This revision is now accepted and ready to land.Mar 5 2014, 6:50 PM