otto-de
feat(rule): readd guidelines for cursor-based pagination
@maxedenharter0507 is there prior discussion that can be linked here other than the (internal) meeting minutes of the last CoP?
Also, I noticed that the Cursor approach in that commit only addresses transparent cursors while there also is a very legitimate aproach of opaque (aka encoded) cursors which brings some very interesting benefits. Some writeups on the matter can be found from Slack and GraphQL. Has there been discussion about this already in the past?
Hi @kiriakos, there is the MS Teams conversation, but as we are here in our public repository, it makes no sense to link it. Aside from that, it does not really contain any deep discussion on that topic. So I'm happy that you started the discussion, and I hope there will be some more comments.
I don't think that we had any discussions about opaque cursors, but i like the idea. On the other side it will force consumers to use our HAL links for navigating through the pages, because the consumer will not know the internal format of the underlying opaque token.
Can you take a look at this PR, @thomasklinger1234 @jensfischer1515, thx :)
As there is no more reaction to this PR. I assume there is no need to reintroduce cursor-based pagination anymore.