[cloud_firestore] Cleanest way to do pagination in abstract service class

[tzvc]

I'm implementing pagination for my Flutter app with Firestore and I am running into a design issue.

I'm using services class to abstract database operation from the business logic of my app through data model class like so:

UI <- business logic (riverpod) <- data model class <- stateless firestore service

This works great as it follows the separation of concerns principles.

However, in the Firestore library, the only way to implement pagination is to save the last DocumentSnapshot to reference it in the next query using startAfterDocument(). This means, as my database services are stateless, I would need to save this DocumentSnapshot in my business logic code, who should in principle be completely abstracted from Firestore.

My first instinct would be to reconstruct a DocumentSnapshot from my data model class inside the service and use that for the pagination, but I would not be able to reconstruct it completely so I wonder if that would be enough.

Has anyone run into this issue? How did you solve it?

Cheers!