Why is next support commented out?

[Joe]

I see the issue https://github.com/POData/POData/issues/76 but it doesn't explain why the implementation of JsonLightODataWriter->writeNextPageLink() is commented out.  What is the problem that prevents this from working? 

I'm in a situation where I really need to get "odata.nextLink" in v3 working so that clients can paginate through large result sets.  Any advice/suggestions/hints would be greatly appreciated!

[drdamour]

i think it's commented just because the tests fail if it's there.  The tests fail because I didn't get to writing tests for writing the next link optionally (only when there is a next).  You can uncomment it and give it a try, but the next link will always be there...so you won't know very well when you get to the end of the set, other than doing math with the count field.

[Joe]

Thanks!  Quick followup question: I managed to get nextLink working so I now get what looks like a valid "odata.nextLink" attribute on paged queries, but the value of nextLink contains $skiptoken, and when I query that URL, $skiptoken appears to be ignored and the results are as if $skiptoken wasn't present.  There seems to be skiptoken support in POData.  Any thoughts on how to deal with this issue?

[drdamour]

oh yeah...darn. $skip and $skiptoken are missing features of OData right now.  Sorry!

[Joe]

$skip totally works in POData, and there seems to be a lot of code in POData that is concerned with $skiptoken, so I was just wondering if maybe you had commented out some crucial bit of code for $skiptoken because tests were failing or something like that?