epriestley f46263903c Fix improper filtering behavior in ConpherenceParticipantQuery ... Summary: Pathway to D17685. This fixes an issue idenified in D17731: if any caller ever queried for more than one participant, some results could get thrown away by re-keying the results on thread PHID: two different participants can be members of the same thread! This also fixes an issue from D17683, where a `needParticipantCache()` callsite was overlooked. Test Plan: - Viewed Conpherence dropdown. - Sent messages, saw unread count / thread order still work properly. Reviewers: chad Reviewed By: chad Differential Revision: https://secure.phabricator.com/D17732		2017-04-19 13:59:47 -07:00
..
__tests__	Use PhutilClassMapQuery instead of PhutilSymbolLoader	2015-08-14 07:49:01 +10:00
aphront	Make "Range" HTTP header work for Celerity static resource requests	2017-04-18 13:46:27 -07:00
applications	Fix improper filtering behavior in ConpherenceParticipantQuery	2017-04-19 13:59:47 -07:00
docs	Fixing of the typos	2017-04-19 11:39:17 -07:00
extensions
infrastructure	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00
view	Disable auto-zoom on mobile form UIs	2017-04-17 15:55:05 -07:00
__phutil_library_init__.php
__phutil_library_map__.php	Remove "participationStatus" from ConpherenceParticipant	2017-04-19 13:58:42 -07:00