epriestley 4ec6990ca7 Implement a rough initial version of ApplicationSearch-driven Conduit read endpoints ... Summary: Ref T9964. See that task for some context and discussion. Ref T7715, which has the bigger picture here. Basically, I want Conduit read endpoints to be full-power, ApplicationSearch-driven endpoints, so that applications can: - Write one EditEngine and get web + conduit writes for free. - Write one SearchEngine and get web + conduit reads for free. I previously made some steps toward this, but this puts more of the structure in place. Test Plan: Viewed API console endpoint and read 20 pages of docs: {F1021961} Made various calls: with query keys, constraints, pagination, and limits. Viewed new {nav Config > Modules} page. Reviewers: chad Reviewed By: chad Maniphest Tasks: T7715, T9964 Differential Revision: https://secure.phabricator.com/D14743		2015-12-11 15:27:06 -08:00
..
PasteConduitAPIMethod.php	Rename Conduit classes	2014-07-25 10:54:15 +10:00
PasteCreateConduitAPIMethod.php	Fix no-op transaction error on paste.create Conduit API method	2015-11-08 07:09:53 -08:00
PasteEditConduitAPIMethod.php	Allow ApplicationEditor forms to be reconfigured	2015-11-10 10:24:40 -08:00
PasteInfoConduitAPIMethod.php	phtize all the things	2015-05-22 21:16:39 +10:00
PasteQueryConduitAPIMethod.php	phtize all the things	2015-05-22 21:16:39 +10:00
PasteSearchConduitAPIMethod.php	Implement a rough initial version of ApplicationSearch-driven Conduit read endpoints	2015-12-11 15:27:06 -08:00