Mitar

Is there anything new about this?

What do you mean by defaults? Yes, I think for now it could be opt-in. I would name it `gl.projects.list(use_keyset_pagination=True)`, which would then prevent one to configure ordering. You could...

Awesome, thanks!

So this just makes "next page link" use `id_after` instead of pagination? So we do not have to modify it ourselves? That is nice. My main motivation behind this issue...

But when fetching all results, it does not matter in which order we fetch? So we should use keyset pagination to assure that we fetch really all results (other modes...

Sorry to nitpick here, feel free to start ignoring me. :-) But, see [here](https://python-gitlab.readthedocs.io/en/stable/api-usage.html#pagination): > By default GitLab does not return the complete list of items. Use the `all` parameter...

> But we could make all=true use keyset generation by default, that's true. That is all I am asking. Plus some documentation pointing out the importance of keyset pagination, so...

I think having common patterns exposed easily in the wrapper is sensible. If you worry about backwards compatibility though, then or we add a special argument, or just document this...

Sorry for late reply. Where are no IDs? For which endpoint? I think it is beneficial if can provide for as many endpoints keyset pagination by default when it is...

You are right that some GitLab API endpoints do not support keyset pagination and that was a surprise for me. Example is [list merge requests](https://docs.gitlab.com/ee/api/merge_requests.html#list-merge-requests). I opened a [GitLab issue...