epriestley a067f64ebb Support export engine extensions and implement an extension for custom fields ... Summary: Depends on D18953. Ref T13049. Allow applications and infrastructure to supplement exportable fields for objects. Then, implement an extension for custom fields. Only a couple field types (int, string) are supported for now. Test Plan: Added some custom fields to Users, populated them, exported users. Saw custom fields in the export. Reviewers: amckinley Reviewed By: amckinley Maniphest Tasks: T13049 Differential Revision: https://secure.phabricator.com/D18954		2018-01-29 15:59:58 -08:00
..
config	[Redesign] Remove remaining barColor callsites	2015-05-28 15:17:34 -07:00
datasource	Support "Select" custom fields in Herald rules	2015-07-16 14:12:54 -07:00
editor	Support tokenizer custom fields in bulk editor	2018-01-19 13:16:46 -08:00
engineextension	Organize bulk edit actions into nice groups	2018-01-19 13:22:25 -08:00
exception	Mark some strings for translation	2015-06-09 23:06:52 +10:00
field	Support export engine extensions and implement an extension for custom fields	2018-01-29 15:59:58 -08:00
herald	Support "Set X to" as an action in Herald for tokenizer/datasource custom fields	2017-11-28 13:41:52 -08:00
interface	Further simplify PhabricatorCustomFieldInterface	2013-08-14 12:34:09 -07:00
parser	Prevent "commit message magic words" parser from exploding on "reverts aaaa.....aaz"	2015-08-26 09:35:23 -07:00
query	Improve Conduit performance for custom fields	2016-07-31 11:15:58 -07:00
standard	Support export engine extensions and implement an extension for custom fields	2018-01-29 15:59:58 -08:00
storage	Improve Conduit performance for custom fields	2016-07-31 11:15:58 -07:00