Connection pattern (edges, nodes, pageInfo) in GraphQL - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to query the list of nodes in a connection.

GraphQL

query { users { [1] { id name } } }

Drag options to blanks, or click blank then click option'

Anodes

Bedges

CpageInfo

Dinfo

Attempts:

3 left

💡 Hint

Common Mistakes

Using edges instead of nodes when only items are needed.

Trying to query pageInfo for items.

The nodes field directly returns the list of items in the connection.

2fill in blank

medium

Complete the code to get the cursor for each edge in a connection.

GraphQL

query { posts { edges { [1] node { title } } } }

Drag options to blanks, or click blank then click option'

Acursor

Bid

CpageInfo

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to get cursor from node instead of edge.

Using id as cursor.

The cursor field on each edge is used for pagination.

3fill in blank

hard

Fix the error in the query to get pageInfo's hasNextPage field.

GraphQL

query { comments { pageInfo { [1] } } }

Drag options to blanks, or click blank then click option'

Acursor

Bedges

ChasNextPage

Dnodes

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to query nodes or edges inside pageInfo.

Using cursor inside pageInfo.

The hasNextPage field inside pageInfo tells if more pages exist.

4fill in blank

hard

Fill both blanks to query edges with cursor and node id.

GraphQL

query { products { edges { [1] node { [2] } } } }

Drag options to blanks, or click blank then click option'

Acursor

Bname

Cid

DpageInfo

Attempts:

3 left

💡 Hint

Common Mistakes

Putting pageInfo inside edges.

Using name instead of id inside node.

Edges have cursor and node. Inside node, id is a common field.

5fill in blank

hard

Fill all three blanks to query nodes with id and name, and pageInfo hasNextPage.

GraphQL

query { employees { [1] { id name } [2] { [3] } } }

Drag options to blanks, or click blank then click option'

Anodes

BpageInfo

ChasNextPage

Dedges

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing edges and nodes incorrectly.

Querying hasNextPage outside pageInfo.

Use nodes for items, pageInfo for pagination info, and inside pageInfo query hasNextPage.

Practice

1. What is the main purpose of the pageInfo field in the GraphQL connection pattern?

easy

A. To define the schema of the connection

B. To list all the nodes in the connection

C. To provide information about pagination like if there are more pages

D. To store the actual data items

Solution

1. Step 1: Understand the role of pageInfo

   The pageInfo field contains metadata about pagination such as whether there are more pages available.

2. Step 2: Differentiate from edges and nodes

   Unlike edges or nodes which hold data items, pageInfo only provides pagination status.

3. Final Answer:

   To provide information about pagination like if there are more pages -> Option C

4. Quick Check:

   pageInfo = pagination info [OK]

Hint: Remember pageInfo tells if more pages exist [OK]

Common Mistakes:

• Confusing pageInfo with nodes or edges
• Thinking pageInfo holds actual data items
• Ignoring pagination metadata role

2. Which of the following is the correct way to query the edges and node fields in a GraphQL connection?

easy

A. { users { edge { node { id name } } } }

B. { users { nodes { id name } } }

C. { users { pageInfo { hasNextPage } } }

D. { users { edges { node { id name } } } }

Solution

1. Step 1: Recall correct field names in connection pattern

   The connection pattern uses edges (plural) and inside each edge a node (singular) holds the data.

2. Step 2: Check each option's syntax

   { users { edges { node { id name } } } }

   correctly uses edges and node.

   { users { nodes { id name } } }

   uses nodes which is valid but not with edges.

   { users { pageInfo { hasNextPage } } }

   queries only pageInfo.

   { users { edge { node { id name } } } }

   uses edge singular which is incorrect.

3. Final Answer:

   { users { edges { node { id name } } } } -> Option D

4. Quick Check:

   edges plural, node singular inside edges [OK]

Hint: Edges is plural; node is singular inside edges [OK]

Common Mistakes:

• Using 'edge' instead of 'edges'
• Mixing nodes and edges syntax
• Querying pageInfo instead of data fields

3. Given this GraphQL query:

{ posts(first: 2) { edges { cursor node { id title } } pageInfo { hasNextPage } } }

And the server returns two posts with ids 101 and 102, what will pageInfo.hasNextPage be if there are more posts after these two?

medium

A. true

B. false

C. null

D. undefined

Solution

1. Step 1: Understand the meaning of hasNextPage

   hasNextPage is true if more items exist beyond the current page.

2. Step 2: Apply to given scenario

   Since the server returns 2 posts but more posts exist after them, hasNextPage must be true.

3. Final Answer:

   true -> Option A

4. Quick Check:

   More posts after current page means hasNextPage = true [OK]

Hint: More items after current page means hasNextPage true [OK]

Common Mistakes:

• Assuming hasNextPage is false when items equal page size
• Confusing hasNextPage with hasPreviousPage
• Expecting null or undefined instead of boolean

4. You wrote this GraphQL query:

{ comments { edge { node { id text } } } }

But it returns an error. What is the likely cause?

medium

A. The field 'node' should be 'nodes'

B. The field should be 'edges' not 'edge'

C. Missing 'pageInfo' field causes error

D. The query must include 'pageInfo' and 'nodes' together

Solution

1. Step 1: Check the connection field names

   The connection pattern uses edges (plural) not edge (singular).

2. Step 2: Identify the error cause

   Using edge causes a field not found error because the schema expects edges.

3. Final Answer:

   The field should be 'edges' not 'edge' -> Option B

4. Quick Check:

   edges plural required, edge singular causes error [OK]

Hint: Use 'edges' plural, not 'edge' singular [OK]

Common Mistakes:

• Using 'edge' instead of 'edges'
• Thinking 'node' should be plural
• Assuming pageInfo is mandatory for query success

5. You want to fetch a list of products with their IDs and names using the connection pattern. You only need the list of products without pagination info. Which query is best?

hard

A. { products { nodes { id name } } }

B. { products { edges { node { id name } } pageInfo { hasNextPage } } }

C. { products { pageInfo { hasPreviousPage } } }

D. { products { edges { cursor } } }

Solution

1. Step 1: Understand the difference between nodes and edges

   nodes gives a simple list of items without pagination details, while edges includes cursors for pagination.

2. Step 2: Choose the query matching the need

   Since pagination info is not needed, querying nodes directly is simpler and efficient.

3. Final Answer:

   { products { nodes { id name } } } -> Option A

4. Quick Check:

   Use nodes for simple list without pagination [OK]

Hint: Use nodes for simple lists without pagination [OK]

Common Mistakes:

• Using edges and pageInfo when not needed
• Querying only pageInfo without data
• Ignoring simpler nodes field for lists