GraphQL Queries

# CHAPTER 7

GraphQL Queries #

1. Introduction #

2. Learning Objectives #

• Structure a basic GraphQL Query.

• Understand how fields map exactly to the JSON response.

• Traverse object relationships using Nested Queries.

• Use the query keyword properly in requests.

3. Beginner-Friendly Explanation #

A GraphQL query navigates data in the exact same way. You start at the top level (the Root Query). If you ask for an object (like a User), you must open the curly braces {} to go inside that object and ask for specific files (Scalars like Name or Age). If the User has a relationship with another object (like Friends), you open another set of curly braces inside the first one to dig deeper. It is a visual representation of the data you want back.

4. Real-World Examples #

• Blog Application: To render a blog homepage, you need a list of posts. But for each post, you also need the author's name, and for the author, you need their profile picture URL. Instead of hitting 3 different API endpoints, a nested GraphQL query fetches this entire hierarchy at once.

• Organization Chart: Fetching a company's CEO, the Managers who report to the CEO, and the Employees who report to the Managers, all in one structured JSON tree.

5. Detailed Code Examples #

type Author {
  id: ID!
  name: String!
  posts: [Post]
}

type Post {
  title: String!
  views: Int!
}

type Query {
  getAuthor(id: ID!): Author
}

The Query: We use the query keyword (which is actually optional for simple queries, but best practice to include) to fetch the data.

query FetchAuthorData {
  getAuthor(id: "1") {
    name
    posts {
      title
      views
    }
  }
}

*(Notice FetchAuthorData - this is the "Operation Name". It is like naming a function. It's optional but highly recommended for debugging.)*

6. Response Structure Example #

The JSON Response:

{
  "data": {
    "getAuthor": {
      "name": "Jane Austen",
      "posts": [
        {
          "title": "Pride and Prejudice",
          "views": 50000
        },
        {
          "title": "Emma",
          "views": 35000
        }
      ]
    }
  }
}

7. Mutation Examples #

mutation {
  deletePost(id: "42") {
    title
    author {
      name
    }
  }
}

8. Schema Examples (Root Query) #

type Query {
  # These are the top-level entry points
  allBooks: [Book]
  singleBook(id: ID!): Book
  me: User
}

9. Best Practices #

• Always Name Your Queries: Instead of just query { ... }, use query GetUserProfile { ... }. When an error occurs on the server, the logs will show the Operation Name, making debugging much easier.

• Only Ask For What You Need: Just because you *can* fetch a user's entire post history in one query doesn't mean you should. Only select the fields required for the current UI component.

• Avoid Over-Nesting: Queries that nest too deeply (e.g., user -> friends -> friends -> friends) can cause massive database load. We will discuss query depth limiting in the security chapter.

10. Common Mistakes #

• Forgetting to select sub-fields: If a field returns an Object (like author: Author), you cannot just ask for author. You *must* open curly braces and ask for a scalar inside it: author { name }. GraphQL will throw an error if you leave off the selection set for an object.

• Assuming order matters: In JSON, key order does not technically matter, but GraphQL guarantees that the response fields will be ordered exactly as you requested them in your query.

11. Mini Exercises #

1. 1. Look at the query in Section 5. Remove the views field. How will the JSON response change?

1. 2. If getAuthor returns a list [Author], do you change how you write the selection set? (Answer: No, the syntax inside the braces remains the same whether it's one object or an array of objects).

12. Coding Challenges #

13. MCQs with Answers #

14. Interview Questions #

• Q: How does a GraphQL Query differ conceptually from a REST GET request?

• Q: Why is it considered best practice to name your operations (queries/mutations)?

• Q: Explain how nested querying solves the "Under-fetching" problem.

15. FAQs #

query {
  me { name }
  topProducts { price }
}

16. Summary #

17. Next Chapter Recommendation #