Why Inline fragments in GraphQL? - Purpose & Use Cases

The Big Idea

What if you could ask for exactly what you want from mixed data without sorting it yourself?

The Scenario

Imagine you have a big box of mixed toys: cars, dolls, and blocks. You want to list only the cars with their special features, but you have to look at each toy one by one and guess if it is a car before writing down its details.

The Problem

Doing this by hand is slow and confusing. You might miss some cars or mix up details from dolls or blocks. It's hard to keep track and easy to make mistakes when sorting and describing each toy separately.

The Solution

Inline fragments let you tell the system exactly how to pick and show details for each type inside a mixed group. You write one query that says, "If this is a car, show these features," and it automatically skips the rest. This saves time and avoids errors.

Before vs After

✗ Before

query { toys { id name ... on Car { wheels engine } ... on Doll { hairColor } } }

✓ After

query { toys { id name ... on Car { wheels engine } } }

What It Enables

Inline fragments make it easy to get just the right details from mixed data without extra work or confusion.

Real Life Example

When building a shopping app, you can fetch different product types in one request and show only the relevant info for each, like size for clothes and battery life for electronics.

Key Takeaways

Manual filtering of mixed data is slow and error-prone.

Inline fragments let you specify type-based selections inside one query.

This makes data fetching cleaner, faster, and less confusing.