epriestley 5030ba0401 Roughly generate transaction-oriented API methods from EditEngines ... Summary: Ref T5873. Ref T9132. This is really rough and feels pretty flimsy at the edges (missing validation, generality, modularity, clean error handling, etc) but gets us most of the way toward generating plausible "whatever.edit" Conduit API methods from EditEngines. These methods are full-power methods which can do everything the edit form can, automatically support the same range of operations, and update when new fields are added. Test Plan: - Used new `paste.edit` to create a new Paste. - Used new `paste.edit` to update an existing paste. - Applied a variety of different transactions. - Hit a reasonable set of errors. {F941144} {F941145} {F941146} {F941147} Reviewers: chad Reviewed By: chad Maniphest Tasks: T5873, T9132 Differential Revision: https://secure.phabricator.com/D14393		2015-11-03 10:12:37 -08:00
..
__tests__	Use PhutilClassMapQuery instead of PhutilSymbolLoader	2015-08-14 07:49:01 +10:00
aphront	Set a property so that unit tests run on PHP7	2015-10-26 21:15:45 +00:00
applications	Roughly generate transaction-oriented API methods from EditEngines	2015-11-03 10:12:37 -08:00
docs	Remove some low-hanging buildStandardPageResponse() methods	2015-11-03 10:11:36 -08:00
extensions	Add src/extensions/ to Phabricator	2013-08-14 15:38:06 -07:00
infrastructure	Add styling for new Remarkup highlighter	2015-11-02 13:20:07 -08:00
view	Implement a basic version of ApplicationEditor in Paste	2015-11-03 10:11:54 -08:00
__phutil_library_init__.php	Delete license headers from files	2012-11-05 11:16:51 -08:00
__phutil_library_map__.php	Roughly generate transaction-oriented API methods from EditEngines	2015-11-03 10:12:37 -08:00