What is the reason for having edges and nodes in a connection in your graphql schema? : <p>I am trying to understand more complex graphql apis that implement the <a href="https://facebook.github.io/relay/graphql/connections.htm" rel="noreferrer">Relay Cursor Connections Specification</a></p>

<p>If you look at the query below that I run on the <a href="https://developer.github.com/early-access/graphql/explorer/" rel="noreferrer">github graphql api explorer</a></p>

<pre><code>{
  repository(owner: "getsmarter", name: "moodle-api") {
    id
    issues(first:2 ) {
      edges {
        node {
          id
          body
        }
      }
      nodes {
        body
      }
      pageInfo {
        endCursor
        hasNextPage
        hasPreviousPage
        startCursor
      }
      totalCount
    } 
  }
}
</code></pre>

<p>Notice it has the fields <strong>edges</strong> and <strong>nodes</strong>.</p>

<p>Why does github have an additional field called nodes in their api? Why don’t they just use the edges field since you can get the same data from edges? Is this just for convenience? </p>
