"page" REST API parameter is confusing

[mitar]

Preflight checklist

• I could not find a solution in the existing issues, docs, nor discussions.
• I agree to follow this project's Code of Conduct.
• I have read and am following this repository's Contribution Guidelines.
• This issue affects my Ory Cloud project.
• I have joined the Ory Community Slack.
• I am signed up to the Ory Security Patch Newsletter.

Describe the bug

Reading here it says:

Pages are created based on the values of per_page and page provided in the querystring, where per_page is the page size, and page is the current page.
In most scenarios, the per_page should be a multiple of the page.

And example has the current page at 10, page size at 5, and then the next page is 15. This looks to me like page should be named offset. page is generally used when you compute offset by doing page * per_page. How it is used in Kratos it should be named offset.

Reproducing the bug

See description above.

Relevant log output

No response

Relevant configuration

No response

Version

v0.8.0-alpha.3

On which operating system are you observing this issue?

Linux

In which environment are you deploying?

Docker Compose

Additional Context

No response

[aeneasr]

In Kratos page is a page and not an offset and you don't need to compute the page, it's always sequential (1,2,3,4,5). Could you update the docs with a wording that makes that easier to understand for you?

[mitar]

I mean, the example is then wrong. The example has previous/next links and they increase in the per_page amount. I can make a PR.

[mitar]

PR: #2143