epriestley 6e4f508beb Provide "builtin" high-level result orders ... 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. Reviewers: btrahan Reviewed By: btrahan Subscribers: epriestley Maniphest Tasks: T7803 Differential Revision: https://secure.phabricator.com/D12379		2015-04-13 11:58:34 -07:00
..
application	Expose all application mail receivers	2015-04-01 11:52:02 -07:00
constants	Apply some autofix linter rules	2014-09-10 06:55:05 +10:00
controller	Convert all tokenizers to take token/scalar inputs	2015-03-31 14:10:55 -07:00
edge	Modernize Ponder edge types	2015-01-01 11:20:22 +11:00
editor	Add addLinkSection to MailBody to properly format URIs	2014-10-30 15:24:10 -07:00
feed	Ponder - make feed stories and emails a bit better	2013-09-18 15:15:25 -07:00
mail	Expose all application mail receivers	2015-04-01 11:52:02 -07:00
phid	Fix broken handle rendering in Ponder	2014-08-12 12:25:58 -07:00
query	Provide "builtin" high-level result orders	2015-04-13 11:58:34 -07:00
remarkup	Remarkup - add a regex to blacklist what objects get link	2014-08-14 15:20:45 -07:00
search	Rename PHIDType classes	2014-07-24 08:05:46 +10:00
storage	Fix visiblity of LiskDAO::getConfiguration()	2015-01-14 06:54:13 +11:00
view	Remove flavor text for action buttons	2014-04-18 17:51:46 -07:00