epriestley a74d602b3c Make stored custom fields work with v3 EditEngine API ... 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. Reviewers: chad Reviewed By: chad Maniphest Tasks: T11114 Differential Revision: https://secure.phabricator.com/D17068		2016-12-16 10:09:03 -08:00
..
__tests__	Use PhutilClassMapQuery instead of PhutilSymbolLoader	2015-08-14 07:49:01 +10:00
aphront	Fix an issue where unexpected debugging output would run afoul of automatic compression	2016-12-14 07:27:08 -08:00
applications	Make stored custom fields work with v3 EditEngine API	2016-12-16 10:09:03 -08:00
docs	Make the documentation more clear that storage.mysql-engine.max-size is measured in bytes	2016-12-13 07:34:20 -08:00
extensions
infrastructure	Replace Differential Edit controller with EditEngine-driven EditPro controller	2016-12-14 07:27:39 -08:00
view	Reorganize phui-object-item CSS, add drag ui	2016-12-14 11:53:17 -08:00
__phutil_library_init__.php
__phutil_library_map__.php	Drive CLI-based revision edits through "differential.revision.edit" API + EditEngine	2016-12-16 10:08:49 -08:00