Page MenuHomePhabricator

[lib] Make sure thick threads starts out with startReached
ClosedPublic

Authored by ashoat on Jul 20 2024, 9:43 PM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 17, 7:05 PM
Unknown Object (File)
Fri, Mar 14, 5:49 AM
Unknown Object (File)
Tue, Mar 11, 6:38 AM
Unknown Object (File)
Mon, Mar 3, 9:20 AM
Unknown Object (File)
Fri, Feb 21, 2:55 AM
Unknown Object (File)
Fri, Feb 21, 2:55 AM
Unknown Object (File)
Fri, Feb 21, 2:53 AM
Unknown Object (File)
Thu, Feb 20, 2:13 AM
Subscribers
None

Details

Summary

In order to make sure that startReached starts out as true when a thread is created, we set truncationStatus to "exhaustive".

I thought about always using exhaustive, but this conflicts with our plans in the Limit number of displayed DMs project, where we'll want startReached to be false if there are messages in SQLite that are not represented in Redux.

Depends on D12827

Test Plan

I followed the test plan described in this Linear comment. Before this diff, the spinner was visible in the newly-created thick thread. After this diff, it was no longer visible

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable