Skip to content

Commit edc45e4

Browse files
committed
Editorial: Clarify intro for inline fragments
Avoid repeating phase about type conditions and refer to prior section. Improve phrasing and include reference to directive application
1 parent 3885a64 commit edc45e4

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

spec/Section 2 -- Language.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -667,10 +667,13 @@ be present and `likers` will not. Conversely when the result is a `Page`,
667667

668668
InlineFragment : ... TypeCondition? Directives? SelectionSet
669669

670-
Fragments can be defined inline within a selection set. This is done to
671-
conditionally include fields based on their runtime type. This feature of
672-
standard fragment inclusion was demonstrated in the `query FragmentTyping`
673-
example. We could accomplish the same thing using inline fragments.
670+
Fragments can also be defined inline within a selection set. This is useful for
671+
conditionally including fields based on a type condition or applying a directive
672+
to a selection set.
673+
674+
This feature of standard fragment inclusion was demonstrated in the
675+
`query FragmentTyping` example above. We could accomplish the same thing using
676+
inline fragments.
674677

675678
```graphql example
676679
query inlineFragmentTyping {

0 commit comments

Comments
 (0)