Skip to content

Commit 6a77223

Browse files
committed
clarify execution language vs. SDL or ootb directives
1 parent 111b1b4 commit 6a77223

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

website/pages/docs/using-directives.mdx

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -18,14 +18,13 @@ custom directives, and how to implement directive behavior during execution.
1818

1919
## How GraphQL.js handles built-in directives
2020

21-
GraphQL defines built-in directives that control query execution or describe metadata
22-
about the schema. These include:
21+
GraphQL defines several built-in directives, each serving a specific purpose during
22+
execution or in the schema. These include:
2323

24-
- `@include` and `@skip`: Conditionally include or skip fields
25-
- `@deprecated`: Marks fields or enum values as deprecated
26-
27-
In GraphQL.js, these directives are handled automatically by the executor or introspection system.
28-
You don't need to write custom logic to support them.
24+
- `@include` and `@skip`: Used in the execution language to conditionally include or skip
25+
fields and fragments at runtime.
26+
- `@deprecated`: Used in Schema Definition Language (SDL) to mark fields or enum values as
27+
deprecated, with an optional reason. It appears in introspection but doesn't affect query execution.
2928

3029
For example, the `@include` directive conditionally includes a field based on a Boolean variable:
3130

0 commit comments

Comments
 (0)