Filtering arguments in GraphQL - Step-by-Step Execution

Concept Flow - Filtering arguments

Start Query

↓

Receive Filtering Arguments

↓

Apply Filters to Data

↓

Return Filtered Results

↓

End Query

The query starts by receiving filtering arguments, applies these filters to the data, and returns only the matching results.

Execution Sample

GraphQL

query {
  books(filter: {author: "Alice", year: 2020}) {
    title
    author
    year
  }
}

This query asks for books written by Alice in the year 2020, returning their title, author, and year.

Execution Table

Step	Filter Argument	Data Checked	Match?	Action	Output
1	author = 'Alice'	{title: 'Book A', author: 'Alice', year: 2020}	Yes	Include	{title: 'Book A', author: 'Alice', year: 2020}
2	author = 'Alice'	{title: 'Book B', author: 'Bob', year: 2020}	No	Exclude
3	year = 2020	{title: 'Book C', author: 'Alice', year: 2019}	No	Exclude
4	author = 'Alice' and year = 2020	{title: 'Book D', author: 'Alice', year: 2020}	Yes	Include	{title: 'Book D', author: 'Alice', year: 2020}
5	author = 'Alice' and year = 2020	{title: 'Book E', author: 'Alice', year: 2021}	No	Exclude
6	-	-	-	Return filtered list	[{title: 'Book A', author: 'Alice', year: 2020}, {title: 'Book D', author: 'Alice', year: 2020}]

💡 All data checked; only books matching author 'Alice' and year 2020 included.

Variable Tracker

Variable	Start	After 1	After 2	After 3	After 4	After 5	Final
filteredResults	[]	[Book A]	[Book A]	[Book A]	[Book A, Book D]	[Book A, Book D]	[Book A, Book D]

Key Moments - 2 Insights

Why is 'Book B' excluded even though it has the correct year?

Because the filter requires author to be 'Alice' and 'Book B' author is 'Bob' (see execution_table row 2). Both conditions must be true.

Why is 'Book C' excluded even though the author matches?

Because the year must be 2020, but 'Book C' has year 2019 (see execution_table row 3). Both filters apply together.

Visual Quiz - 3 Questions

Look at the execution table, which book is included at step 4?

A Book C

B Book B

C Book D

D Book E

💡 Hint

Check the 'Output' column at step 4 in the execution_table.

At which step does the filter exclude a book because the author does not match?

A Step 3

B Step 2

C Step 5

D Step 1

💡 Hint

Look at the 'Match?' column and see which step has 'No' due to author mismatch.

If the filter changed to only author = 'Alice', which step's exclusion would change?

A Step 5

B Step 3

C Step 2

D Step 4

💡 Hint

Check which step excludes due to year mismatch when author matches.

Concept Snapshot

Filtering arguments in GraphQL let you specify conditions to get only matching data.
Syntax: field(filter: {key: value, ...})
Filters apply together (AND logic).
Only data matching all filters is returned.
Useful to narrow down query results easily.

Full Transcript

In GraphQL, filtering arguments help you get only the data you want by specifying conditions. The query starts by receiving these filters, then checks each data item against them. If the item matches all conditions, it is included in the results; otherwise, it is excluded. For example, filtering books by author and year returns only books matching both. This process continues until all data is checked, and the filtered list is returned. Understanding how each filter applies together helps avoid confusion about why some data is excluded.

Practice

1.

What is the main purpose of filtering arguments in a GraphQL query?

easy

A. To get only the data you need by specifying conditions

B. To change the structure of the data returned

C. To add new data to the database

D. To delete data from the database

Solution

1. Step 1: Understand filtering arguments

   Filtering arguments are used to specify conditions that limit the data returned by a query.

2. Step 2: Identify the purpose in the context of data retrieval

   They help get only the data you need, making queries efficient and faster.

3. Final Answer:

   To get only the data you need by specifying conditions -> Option A

4. Quick Check:

   Filtering arguments = get needed data [OK]

Hint: Filtering arguments limit data returned by conditions [OK]

Common Mistakes:

• Thinking filtering changes data structure
• Confusing filtering with data modification
• Assuming filtering adds or deletes data

2.

Which of the following is the correct syntax to filter users by age greater than 25 in a GraphQL query?

{
  users(age_gt: 25) {
    id
    name
  }
}

easy

A. { users(age: {gt: 25}) { id name } }

B. { users(age_gt: 25) { id name } }

C. { users(filter: {age: 25}) { id name } }

D. { users(age > 25) { id name } }

Solution

1. Step 1: Identify correct GraphQL filter syntax

   GraphQL uses argument names like age_gt to filter values greater than 25.

2. Step 2: Compare options with standard syntax

   { users(age_gt: 25) { id name } } uses age_gt: 25 correctly; others use invalid or incorrect syntax.

3. Final Answer:

   { users(age_gt: 25) { id name } } -> Option B

4. Quick Check:

   Correct filter syntax = { users(age_gt: 25) { id name } } [OK]

Hint: Use _gt suffix for 'greater than' filters [OK]

Common Mistakes:

• Using operators like > inside arguments
• Passing filter as nested object incorrectly
• Using equality instead of greater than

3.

Given the query below, what will be the output if the database has users with ages 20, 30, and 40?

{
  users(age_gte: 30) {
    name
  }
}

medium

A. [{"name": "User30"}, {"name": "User40"}]

B. [{"name": "User20"}]

C. [{"name": "User20"}, {"name": "User30"}, {"name": "User40"}]

D. []

Solution

1. Step 1: Understand the filter age_gte: 30

   This filter returns users with age greater than or equal to 30.

2. Step 2: Check which users match the condition

   Users with ages 30 and 40 match; user with age 20 does not.

3. Final Answer:

   [{"name": "User30"}, {"name": "User40"}] -> Option A

4. Quick Check:

   age_gte 30 returns users 30 and 40 [OK]

Hint: gte means greater than or equal [OK]

Common Mistakes:

• Including users younger than 30
• Confusing gte with gt
• Returning empty list incorrectly

4.

Identify the error in the following GraphQL query that tries to filter products by price less than 100:

{
  products(price_lt 100) {
    id
    name
  }
}

medium

A. Incorrect field name 'products' instead of 'productList'

B. Using wrong filter suffix 'lt' instead of 'lessThan'

C. Missing curly braces around filter argument

D. Missing colon ':' between argument name and value

Solution

1. Step 1: Check argument syntax in the query

   The argument price_lt 100 is missing a colon ':' between the argument name and value.

2. Step 2: Confirm correct syntax for filtering

   Correct syntax requires a colon: price_lt: 100.

3. Final Answer:

   Missing colon ':' between argument name and value -> Option D

4. Quick Check:

   Arguments need ':' separator [OK]

Hint: Always use ':' between argument and value [OK]

Common Mistakes:

• Omitting colon ':' after argument name
• Using wrong filter suffix names
• Confusing field names

5.

You want to query a list of books published after 2010 and with more than 300 pages. Which of the following GraphQL queries correctly applies both filters?

{
  books(published_gt: 2010, pages_gt: 300) {
    title
    author
  }
}

hard

A. { books(filter: {published: {gt: 2010}, pages: {gt: 300}}) { title author } }

B. { books(published: {gt: 2010}, pages: {gt: 300}) { title author } }

C. { books(published_gt: 2010, pages_gt: 300) { title author } }

D. { books(published_gt: 2010 pages_gt: 300) { title author } }

Solution

1. Step 1: Understand how to apply multiple filters in GraphQL

   Filters are passed as separate arguments separated by commas.

2. Step 2: Check each option for correct syntax and filter usage

   { books(published_gt: 2010, pages_gt: 300) { title author } } correctly uses commas and proper filter names; others have syntax errors or wrong structure.

3. Final Answer:

   { books(published_gt: 2010, pages_gt: 300) { title author } } -> Option C

4. Quick Check:

   Multiple filters use commas and correct suffixes [OK]

Hint: Separate filters with commas and use _gt suffix [OK]

Common Mistakes:

• Missing commas between arguments
• Using nested filter objects incorrectly
• Omitting colons between argument and value