Joshua Spence acb1eb81cc Move some PhabricatorSearchField subclasses ... Summary: Move some `PhabricatorSearchField` subclasses to be adjacent to the application to which they belong. This seems generally better to me than lumping them all together in the `src/applications/search/field/` directory. I was also wondering if it makes sense to rename these subclasses as `PhabricatorXSearchField` rather than `PhabricatorSearchXField` (as per T5655), but wasn't really sure if these objects are meant to be search-fields, or just fields belonging to the #search application. Test Plan: N/A. Reviewers: #blessed_reviewers, epriestley Reviewed By: #blessed_reviewers, epriestley Subscribers: epriestley, Korvin Differential Revision: https://secure.phabricator.com/D13374		2015-07-06 22:52:05 +10:00
..
application	Expose all application mail receivers	2015-04-01 11:52:02 -07:00
capability	Simplify the implementation of PhabricatorPolicyCapability subclasses	2014-07-25 08:25:42 +10:00
conduit	phtize all the things	2015-05-22 21:16:39 +10:00
config	Remove all application-specific reply handler domains	2015-03-31 16:48:40 -07:00
controller	Remove *TransactionType classes	2015-06-08 11:26:43 +10:00
editor	Remove *TransactionType classes	2015-06-08 11:26:43 +10:00
mail	phtize all the things	2015-05-22 21:16:39 +10:00
markup	Don't require memes to be at the end of a line	2015-05-07 11:09:14 -07:00
phid	Rename PHIDType classes	2014-07-24 08:05:46 +10:00
query	Move some PhabricatorSearchField subclasses	2015-07-06 22:52:05 +10:00
storage	Remove *TransactionType classes	2015-06-08 11:26:43 +10:00
typeahead	Give typeahead browse dialogs sensible titles	2015-04-20 10:06:23 -07:00