Commit 960a7548 authored by Natalia Tepluhina's avatar Natalia Tepluhina

Removed a note about pagination limitations

parent 0f896bd4
...@@ -411,18 +411,6 @@ fetchNextPage() { ...@@ -411,18 +411,6 @@ fetchNextPage() {
Please note we don't have to save `pageInfo` one more time; `fetchMore` triggers a query Please note we don't have to save `pageInfo` one more time; `fetchMore` triggers a query
`result` hook as well. `result` hook as well.
#### Limitations
Currently, bidirectional pagination doesn't work:
- `hasNextPage` returns a correct value only when we paginate forward using `endCursor`
and `first` parameters.
- `hasPreviousPage` returns a correct value only when we paginate backward using
`startCursor` and `last` parameters.
This should be resolved in the scope of the issue
[Bi-directional Pagination in GraphQL doesn't work as expected](https://gitlab.com/gitlab-org/gitlab/-/issues/208301).
### Testing ### Testing
#### Mocking response as component data #### Mocking response as component data
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment