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
F14057299: D14743.diff
Sun, Nov 17, 2:04 AM
F14022863: D14743.diff
Wed, Nov 6, 8:16 PM
F14001995: D14743.id.diff
Fri, Oct 25, 2:05 PM
F13971187: D14743.id35657.diff
Oct 17 2024, 12:11 PM
F13960988: D14743.id35659.diff
Oct 15 2024, 2:27 AM
Unknown Object (File)
Oct 9 2024, 2:50 AM
Unknown Object (File)
Sep 20 2024, 10:44 PM
Unknown Object (File)
Sep 15 2024, 10:01 AM
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

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.