diff options
Diffstat (limited to 'doc/development/graphql_guide/pagination.md')
| -rw-r--r-- | doc/development/graphql_guide/pagination.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/graphql_guide/pagination.md b/doc/development/graphql_guide/pagination.md index 7b9d2158c60..daa39875119 100644 --- a/doc/development/graphql_guide/pagination.md +++ b/doc/development/graphql_guide/pagination.md @@ -20,7 +20,7 @@ See the [general pagination guidelines section](../database/pagination_guideline This is the traditional, page-by-page pagination, that is most common, and used across much of GitLab. You can recognize it by -a list of page numbers near the bottom of a page, which, when clicked, +a list of page numbers near the bottom of a page, which, when selected, take you to that page of results. For example, when you select **Page 100**, we send `100` to the @@ -248,7 +248,7 @@ incorrect sort order. There are times when the [complexity of sorting](#limitations-of-query-complexity) is more than our keyset pagination can handle. -For example, in [`IssuesResolver`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/graphql/resolvers/issues_resolver.rb), +For example, in [`ProjectIssuesResolver`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/graphql/resolvers/project_issues_resolver.rb), when sorting by `priority_asc`, we can't use keyset pagination as the ordering is much too complex. For more information, read [`issuable.rb`](https://gitlab.com/gitlab-org/gitlab/-/blob/master/app/models/concerns/issuable.rb). |