Why capping the OFFSET? Doesn' t make any sense to me, ok LIMIT cap at 1000 is no big deal, it was always documented like that (was already enforced in API v1) and thus anything developed with something going beyond 1000 is aking to fail at some point, but the OFFSET is exactly there to paginate through stuff?
This is a breaking change that will incur cost for customers everywhere or break a lot of communities, paging with the CURSOR is not that easy from the frontend, should we pass the CURSOR via GET param?
Enforcing 1000 LIMIT is one thing, capping OFFSET to 1000 is nonsense and a no-go!
I have a support case open asking for guidance on this. I let them know this will break the pagination on our forum lists and on other customizations. So far, their only response was "use cursor", but I don't think that's possible. I will update here if I get any better response.
I also wonder how many customers are using offset and don't even know it.
Please let me know if you get a better response, otherwise the only solution we can think of to get page X is to cursor through to page X. So if you wanted page 100, you'd have to cursor through 100 pages before displaying the result! Which seems strange...
Exactly! Thanks for pointing that out, don't see how that would put less stress on the API servers =)...
Regarding "I also wonder how many customers are using offset and don't even know it.":
I think A LOT, I have worked on many communities where I have taken over a customized codebase, and I can count the occurrences where CURSOR was used to paginate something on one hand, most use LIMIT/OFFSET...
