You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the message list, when the user scrolls to the top of the messages we have (or near the top), we should make a request to the server and load the next older batch of messages.
Unless we know we already have the oldest messages for the narrow, that is. So we should track that, based on the found_oldestreturned by get-messages (much like in state.caughtUp in zulip-mobile).
This will mean extending MessageListView (the view-model) so that it can add a batch of messages at the beginning of the list, as well as a new message at the end. Probably it should switch from using List for the list of messages to using a deque, like QueueList from package:collection.
then we should at the same time handle fetching newer messages on scrolling to the bottom, and tracking whether we have the newest already. If we do this before those, then we might leave that direction as a note on those issues.
The text was updated successfully, but these errors were encountered:
In the message list, when the user scrolls to the top of the messages we have (or near the top), we should make a request to the server and load the next older batch of messages.
Unless we know we already have the oldest messages for the narrow, that is. So we should track that, based on the
found_oldest
returned by get-messages (much like instate.caughtUp
in zulip-mobile).This will mean extending
MessageListView
(the view-model) so that it can add a batch of messages at the beginning of the list, as well as a new message at the end. Probably it should switch from usingList
for the list of messages to using a deque, like QueueList from package:collection.If we do this after we have either of
then we should at the same time handle fetching newer messages on scrolling to the bottom, and tracking whether we have the newest already. If we do this before those, then we might leave that direction as a note on those issues.
The text was updated successfully, but these errors were encountered: