I wonder if it would be possible to use VirtualScroll and ion-infinite-scroll together. The benefit is to handle result that grows significantly after loading many subsequent chunks. On the other side its mentioned on VirtualScroll performance tips:
Changing the dataset requires the entire virtual scroll to be reset, which is an expensive operation and should be avoided if possible.
I wonder if growing the dataset also requires reseting.
Important point. We need to know (according to the documentation*) if the performance will decrease using virtual scroll with infinite scroll @mhartington
*The data that builds the templates within the virtual scroll. This is the same data that youād pass to ngFor. Itās important to note that when this data has changed, then the entire virtual scroll is reset, which is an expensive operation and should be avoided if possible.
At the moment, they may āworkā, but they definitely can be improved.
This first pass at virtual scroll just add the initial functionality.
But we can expect that virtualScroll will work with things like Pull to refresh and InfiniteScroll.
Virtual scroll should add support for dynamically loading some more, at some pointā¦
Those points, and this āsomeā, should be configurableā¦ I think being able to pass a callback function, at the configured point (like, 75% through total, for example) would be greatā¦ it should be possible.
Would be cool if it was smart enough to handle the āpagingā itself as well. (instead of manually doing offset tricks)