Page MenuHomePhabricator

Implement a rough initial version of ApplicationSearch-driven Conduit read endpoints
ClosedPublic

Authored by epriestley on Dec 11 2015, 7:39 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Apr 30, 11:26 PM
Unknown Object (File)
Sat, Apr 27, 10:56 PM
Unknown Object (File)
Mon, Apr 22, 10:47 PM
Unknown Object (File)
Fri, Apr 19, 3:56 PM
Unknown Object (File)
Thu, Apr 11, 3:58 PM
Unknown Object (File)
Wed, Apr 10, 7:45 AM
Unknown Object (File)
Sat, Apr 6, 9:44 PM
Unknown Object (File)
Mar 31 2024, 6:56 PM
Subscribers
None

Details

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:

Screen Shot 2015-12-11 at 11.38.00 AM.png (1×1 px, 302 KB)

Made various calls: with query keys, constraints, pagination, and limits.

Viewed new ConfigModules page.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Implement a rough initial version of ApplicationSearch-driven Conduit read endpoints.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: chad.
chad edited edge metadata.
This revision is now accepted and ready to land.Dec 11 2015, 9:58 PM
This revision was automatically updated to reflect the committed changes.