Update docs/room-list-store.md

Co-authored-by: J. Ryan Stinnett <jryans@gmail.com>
This commit is contained in:
Travis Ralston 2021-04-02 19:33:16 -06:00 committed by GitHub
parent 343ce3b502
commit af443c4cff
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -145,7 +145,7 @@ expect a change in the condition unless the condition says it has changed. This
maintain the caching behaviour described above. maintain the caching behaviour described above.
One might ask why we don't just use prefilter conditions for everything, and the answer is one of slight One might ask why we don't just use prefilter conditions for everything, and the answer is one of slight
subtly: in the cases of prefilters we are knowingly exposing the user to a workspace-style UX where subtlety: in the cases of prefilters we are knowingly exposing the user to a workspace-style UX where
room notifications are self-contained within that workspace. Runtime filters tend to not want to affect room notifications are self-contained within that workspace. Runtime filters tend to not want to affect
visible notification counts (as it doesn't want the room header to suddenly be confusing to the user as visible notification counts (as it doesn't want the room header to suddenly be confusing to the user as
they type), and occasionally UX like "found 2/12 rooms" is desirable. If prefiltering were used instead, they type), and occasionally UX like "found 2/12 rooms" is desirable. If prefiltering were used instead,