@alexandernst Here's an explanation for my monster TLDR comment above ;). I probably should have broken up that large comment to reference the lines of code to which they applied.

I ended up aliasing the 'hasPrevious' and 'hasNext' properties of the 'information' object in the requestPager to 'previous' and 'next'. I know that these properties aren't really considered to be public, but they were convenient to use in my view to determine pagination boundaries. Perhaps we can consider making some formal public methods '.next' and '.previous' live off of the collection itself.