I’d suggest that if it doesn’t then we should fix one or the other! I’m diving into GraphQL right now and pagination seems to be an open question over there as well, with different options along the complexity-performance-features triangle.
It aligns pretty well I think. But I’m happy to tweak it if need be. For example, I’m not using the find from publication package yet.
And regarding GraphQL, I haven’t looked too much into it yet but my thinking was that people could use this container for now, and then once Apollo is officially out they can just swap the container out for its GraphQL equivalent without having to change the rest of their app.
Can you expand your question a bit further - how would you like to use it with connect? This is a Meteor package, tied pretty closely to Meteor’s data handling model. Meteor leverages connect behind the scenes, but this package relies on a lot of Meteor’s layers built outside of / on top of connect.