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.
This seems to be working well for me. @stefanhofman's original pagination implementation is great, all that I've done is reverted back to a regular
VStack
(after trying aLazyVStack
) as it doesn't seem to be recommended to use a list or lazy stack for content with variable content size (also it doesn't seem possible to hide the table view separators on aList
since iOS 14 so that was a dead end).I added a
ProgressView
spinner at the top of the list which triggers the pagination whenever it comes into view. Needs some future work to hide the spinner if there's no more messages to load.