Best practice for "double" pagination

[attheodo]

New issue checklist

• I have reviewed the README and documentation
• I have searched existing issues and this is not a duplicate

Hello everyone!

We have a list that displays photos grouped by album. Albums and their photos are being retrieved by two different GraphQL queries that return results in a paginated manner. We're planning to use a ListStackedSectionController for each album-and-its-photos item with one section ctrl for the "album header cell" and one section controller to manage all of it's photos.

Wanted to ask if it makes sense to have the pages fetching logic (keeping offsets and issuing network requests for next page of photos) inside the section ctrl that manages the album's photos?

[rnystrom]

I’d def put the paging logic inside each section controller. One note though is that the stacked SC is being deprecated! I’d recommend using the binding SC.

_{Sent with GitHawk}

[moosabaloch]

Any updates on this?
@rnystrom , @attheodo could you please suggest any workaround for implementing pagination in multiple section controllers.