Page MenuHomePhabricator

Provide "builtin" high-level result orders
ClosedPublic

Authored by epriestley on Apr 12 2015, 10:34 PM.
Tags
None
Referenced Files
F15524822: D12379.id29721.diff
Mon, Apr 21, 10:36 AM
F15494828: D12379.diff
Sun, Apr 13, 1:48 AM
F15469951: D12379.diff
Fri, Apr 4, 6:28 PM
F15453326: D12379.diff
Sat, Mar 29, 10:56 AM
F15415100: D12379.id29722.diff
Mar 20 2025, 4:00 AM
Unknown Object (File)
Feb 18 2025, 5:24 PM
Unknown Object (File)
Feb 13 2025, 9:28 PM
Unknown Object (File)
Feb 9 2025, 4:19 AM
Subscribers

Details

Summary

Ref T7803. Currently, available high-level orders are spread across Query and SearchEngine classes and implemented separately for each application.

Lift the concept of "builtin" (high-level, user-facing, named) orders (similar to "builtin" queries in ApplicationSearch) into the root Query class, and let it drive the SearchEngine implementation. This allows you to define a new order in one place and have it automatically work across the entire stack.

This will also let Conduit expose this information in a straightforward way.

Test Plan
  • Used ApplicationSearch in Diffusion.
  • Used all result orderings.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

epriestley retitled this revision from to Provide "builtin" high-level result orders.
epriestley updated this object.
epriestley edited the test plan for this revision. (Show Details)
epriestley added a reviewer: btrahan.
btrahan edited edge metadata.
This revision is now accepted and ready to land.Apr 13 2015, 5:58 PM
This revision was automatically updated to reflect the committed changes.