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
..
ConduitResultSearchEngineExtension.php	Implement a rough initial version of ApplicationSearch-driven Conduit read endpoints	2015-12-11 15:27:06 -08:00
PhabricatorConduitLogQuery.php	Use __CLASS__ instead of hard-coding class names	2015-05-14 07:21:13 +10:00
PhabricatorConduitMethodQuery.php	Have EditEngine API methods provide the correct application to Conduit	2015-11-16 10:02:50 -08:00
PhabricatorConduitSearchEngine.php	Document how to use harbormaster.sendmessage to report lint and unit results	2015-08-04 13:05:52 -07:00
PhabricatorConduitTokenQuery.php	Use __CLASS__ instead of hard-coding class names	2015-05-14 07:21:13 +10:00