Page MenuHomePhabricator

Make stored custom fields work with v3 EditEngine API
ClosedPublic

Authored by epriestley on Dec 16 2016, 2:19 PM.
Tags
None
Referenced Files
F15772311: D17068.id41084.diff
Fri, May 30, 5:15 AM
Unknown Object (File)
Thu, May 29, 8:53 AM
Unknown Object (File)
Wed, May 28, 11:27 AM
Unknown Object (File)
Tue, May 27, 9:10 PM
Unknown Object (File)
Sun, May 25, 8:15 PM
Unknown Object (File)
Apr 28 2025, 10:42 AM
Unknown Object (File)
Apr 27 2025, 4:00 AM
Unknown Object (File)
Apr 26 2025, 8:56 PM
Subscribers
None

Details

Summary

Ref T11114. This makes the unusual stored custom fields ("Blame Rev", "Revert Plan", etc) work somewhat correctly (?) with EditEngine.

Test Plan
  • Created, updated and edited revisions with unusual stored custom fields like "Blame Rev".
  • Observed that these fields now populate in "differential.revision.edit" when available.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Make stored custom fields work with v3 EditEngine API.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Dec 16 2016, 3:21 PM
This revision was automatically updated to reflect the committed changes.