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
..
PonderAnswerQuery.php	Remove getPagingColumn() / getReversePaging()	2015-04-13 11:58:32 -07:00
PonderAnswerTransactionQuery.php	Use application PHIDs for application transactions	2013-07-29 12:04:15 -07:00
PonderQuestionQuery.php	Provide "builtin" high-level result orders	2015-04-13 11:58:34 -07:00
PonderQuestionSearchEngine.php	Convert all tokenizers to take token/scalar inputs	2015-03-31 14:10:55 -07:00
PonderQuestionTransactionQuery.php	Use application PHIDs for application transactions	2013-07-29 12:04:15 -07:00