GraphQL和中继的概念

Pagination is never an easy question and not one explicitly solved by GraphQL. GraphQL provides a data fetching framework, how that framework is used to do things (like pagination) is up to the developer.

The Relay team has attempted to standardize pagination with the cursor connection specification for GraphQL. The cursor connection specification is not unique to Relay and can be used with Angular, the main goal of the specification is to provide a standardized way to work with large collections from a GraphQL server. The main thing to note about this specification is that with every object there is an associated cursor. This associated cursor allows the client to resume pagination from any point in the collection.

If you are interested in implementing the Relay specification I encourage you to read Sashko Stubailo's Understanding pagination: REST, GraphQL, and Relay where he explains the motivation behind the Relay connection specification and explains how to implement it.

To see the connection specification in action, take a look at the example SWAPI GraphQL API which implements the Relay specification in GraphQL. I encourage you to open the documentation window and browse the PeopleConnection. Note how they implement both edges and people fields.

If cursor pagination is too complicated for you to use/implement, you could always expose a traditional limit/offset pagination for your GraphQL API. The interface would probably look something like this:

{
  friends(limit: 5, offset: 20) {
    name
  }
}

最后，您提供的查询来自GraphQL的早期技术预览，并且实际上不符合规范（源）。更合适的查询（如哈菲兹所提到的）将是：

{
  friends(first: 1) {
    cursor
    node {
      name
    }
  }
}

React Europe 2015有两个很棒的演讲，我也建议您观看其中有关GraphQL Without Relay的更多演讲。

• Nick Schrock和Dan Schafer-创建GraphQL服务器
• Lee Byron-探索GraphQL