Skip to content

Commit 2ec4e25

Browse files
Grammar: a page ... which let[s] (graphql#661)
1 parent 9a6e786 commit 2ec4e25

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

site/learn/Learn-Queries.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ In the above example, the two `hero` fields would have conflicted, but since we
9898

9999
## Fragments
100100

101-
Let's say we had a relatively complicated page in our app, which let us look at two heroes side by side, along with their friends. You can imagine that such a query could quickly get complicated, because we would need to repeat the fields at least once - one for each side of the comparison.
101+
Let's say we had a relatively complicated page in our app, which lets us look at two heroes side by side, along with their friends. You can imagine that such a query could quickly get complicated, because we would need to repeat the fields at least once - one for each side of the comparison.
102102

103103
That's why GraphQL includes reusable units called _fragments_. Fragments let you construct sets of fields, and then include them in queries where you need to. Here's an example of how you could solve the above situation using fragments:
104104

0 commit comments

Comments
 (0)