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
F19516280: D14743.id35657.diff
Wed, Jan 14, 10:18 PM
F19508378: D14743.diff
Sat, Jan 10, 3:43 AM
F19508377: D14743.diff
Sat, Jan 10, 3:43 AM
F19152382: D14743.diff
Dec 11 2025, 2:30 AM
F19060346: D14743.diff
Nov 29 2025, 9:13 AM
F18983333: D14743.id35659.diff
Nov 17 2025, 9:00 AM
F18982567: D14743.id35659.diff
Nov 17 2025, 7:05 AM
F18980558: D14743.id35657.diff
Nov 17 2025, 12:56 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.