Fix onStartReached not called when list content is small #42902
Closed
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.
Summary:
Currently if the virtualized list content is small
onStartReached
won't be called initially when the list is mounted. This is because when the content is smallonEndReached
will be called initially preventingonStartReached
from being called. In_maybeCallOnEdgeReached
callingonEndReached
andonStartReached
are in the same conditional so they cannot both be triggered at once. To improve the consistency ofonStartReached
we should call bothonEndReached
andonStartReached
if needed.Changelog:
[GENERAL] [FIXED] - Call onStartReached initially when list is small and
onEndReached
is calledTest Plan:
I used this code to test in RN Tester (replace content of RNTesterAppShared.js)
Before the change only onEndReached is called, after the change both onStartReached and onEndReached is called.