Page MenuHomePhabricator

Modularize Almanac Binding transactions
ClosedPublic

Authored by epriestley on Apr 10 2018, 12:15 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Apr 25, 1:16 AM
Unknown Object (File)
Sat, Apr 20, 11:49 AM
Unknown Object (File)
Fri, Apr 19, 2:51 AM
Unknown Object (File)
Mon, Apr 15, 4:06 PM
Unknown Object (File)
Thu, Apr 11, 8:50 AM
Unknown Object (File)
Thu, Apr 11, 12:04 AM
Unknown Object (File)
Mar 5 2024, 7:23 AM
Unknown Object (File)
Jan 25 2024, 4:15 AM
Subscribers
None

Details

Summary

Depends on D19320. Ref T13120. Ref T12414. Move transactions for Almanac Bindings to ModularTransactions.

Test Plan
  • Created a new binding.
  • Tried to create a duplicate binding, got an error.
  • Edited a binding to rebind it to a different device.
  • Disabled and enabled bindings.
  • Grepped for AlmanacBindingTransaction:: constants.

When a binding is created, it currently renders a bad "changed the interface from ??? to X" transaction. This is because creation isn't currently using EditEngine. I plan to swap it shortly, which will turn this into a real "Create" transaction and fix the issue.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

Note that, for now, Bindings have the same issue as Services in D19317: editing properties works correctly, but doesn't render the right transaction stories in the timeline. Since this is just a display issue, I plan to deal with it after converting everything.

amckinley added inline comments.
src/applications/almanac/xaction/AlmanacBindingInterfaceTransaction.php
62–63

renderOldValue()/renderNewValue()?

This revision is now accepted and ready to land.Apr 10 2018, 3:51 PM
src/applications/almanac/xaction/AlmanacBindingInterfaceTransaction.php
62–63

This one's right -- since the old and new values are PHIDs, this renders nice named links for them.

This revision was automatically updated to reflect the committed changes.