6 Commits (4c1e4f5127bd7fc8a3ab852d630242a704ffbda2)

Author	SHA1	Message	Date
Kegan Dougal	eed7340663	Add additional tests	2023-01-19 15:02:48 +00:00
Kegan Dougal	4db1928bcd	Prettier and strict	2023-01-19 12:49:20 +00:00
Kegan Dougal	7c2dd7224f	unbreak jest tests	2023-01-19 11:15:08 +00:00
Michael Weimann	526645c791	Apply prettier formatting	2022-12-12 12:24:14 +01:00
kegsay	acdcda78f0	sliding sync: add lazy-loading member support (#9530) ... * sliding sync: add lazy-loading member support Also swap to `$ME` constants when referring to our own member event. * Hook into existing LL logic when showing the MemberList * Linting * Use consts in js sdk not react sdk * Add jest tests * linting * Store the room in the test * Fix up getRoom impl * Add MemberListStore * Use the right context in MemberList tests * Fix RightPanel-test * Always return members even if we lazy load * Add MemberListStore tests * Additional tests	2022-11-18 19:05:00 +00:00
kegsay	dcf497d013	sliding-sync: spider all rooms on the user's account for search (#9514) ... * sliding-sync: spider all rooms on the user's account for search On startup, slowly accumulate room metadata for all rooms on the user's account. This is so we can populate the local search cache with enough data for it to function, obviating the need to have separate code paths for sliding sync searches. This will allow spotlight search to work with slow/no network connectivity, though clicking on the room will still require a round trip. This is an explicit request from @ara4n to improve the snapiness of room searches, despite the unbounded bandwidth costs requesting all N rooms on the user's account. * Comments and tweak defaults * Review comments; remove SS search code * bugfix: use setListRanges once the list has been set up If we don't, then we send needless extra data and can cause bugs because setList will wipe the index->room_id map, which trips up SlidingRoomListStore.	2022-11-01 10:27:03 +00:00