fix: Fix loading following messages condition WPB-9465 #17599
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This fixes the part of the problem.
TODO: If messages are all read, the scrolling will trigger the next messages loading. But if the messages (30+ missed calls and some content messages after them) are not read, the scroll to the last message will not trigger the loading, new sent messages will appear, but the missed messages will not be shown
TODO: in most cases
can be replaced with
!conversation.hasLastReceivedMessageLoaded()
, I'd do this refactoring within this fix too.Also, the
isLastReceivedMessage
can be a public method ofconversation
Checklist
Important details for the reviewers
(Delete this section if unnecessary)