Working on implementing this in together now, I'm sure there is a valid reason, but I'm just wondering why the
_id is different from the paging before and after values, could they not be the same?
after values are meant to represent pages of data, not necessarily individual records. In my case, the
after value refers to an item that isn't in the current page. I could return a string for
_id that looks more like the
after strings, but that's just an implementation detail of my server. Alternately I may switch my
after strings to look more like the current
_id value. Either way, this difference doesn't seem important to the client.