Skip to content

Commit 3286074

Browse files
rmschindlerstubailo
authored andcommitted
Update BestPractice-Pagination.md (#632)
1 parent 8865126 commit 3286074

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/learn/BestPractice-Pagination.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ The concept of an edge also proves useful if there is information that is specif
7878

7979
Now we have the ability to paginate through the connection using cursors, but how do we know when we reach the end of the connection? We have to keep querying until we get an empty list back, but we'd really like for the connection to tell us when we've reached the end so we don't need that additional request. Similarly, what if we want to know additional information about the connection itself; for example, how many total friends does R2-D2 have?
8080

81-
To solve both of these problems, our `friends` field can return a connection object. The connection object will then have field for the edges, as well as other information (like total count and information about whether a next page exists). So our final query might look more like:
81+
To solve both of these problems, our `friends` field can return a connection object. The connection object will then have a field for the edges, as well as other information (like total count and information about whether a next page exists). So our final query might look more like:
8282

8383

8484
```graphql

0 commit comments

Comments
 (0)