This document discusses GraphQL directives and how to extend GraphQL with custom directives. It begins by explaining what directives are and provides examples of built-in directives like @include and @deprecated. It then discusses why you would want to create custom directives for things like text formatting, date formatting, and access restrictions. The document dives into how to declare and define a directive as well as how to write a directive resolver. It concludes by introducing the graphql-directive library for easily adding directives and resolving common issues like caching.

1. Extend GraphQL
with directives
@neoziro
smooth-code.com

2. I am Greg Bergé
JavaScript, React & GraphQL trainer
@neoziro
!
github.com/neoziro
"
smooth-code.com#

3. smooth code

4. What is a directive?

5. @include(if: Boolean)

6. Built-in directives

7. @include(if: Boolean!)
@skip(if: Boolean!)
@deprecated(reason: String)

8. @include / @skip
•Query directive
•Can be used on fields and fragments
•Control the scope of query using a
parameter

9. query Person($includeFilms: Boolean = false) {
person(personID: 1) {
name
height
mass
filmConnection(first: 10) @include(if: $includeFilms) {
edges {
node {
title
}
}
}
}
}

10. query Person($skipFilms: Boolean = false) {
person(personID: 1) {
name
height
mass
filmConnection(first: 10) @skip(if: $skipFilms) {
edges {
node {
title
}
}
}
}
}

13. @deprecated
•Schema directive
•Can be used on field definitions and
enums
•Marks an element of a GraphQL
schema as no longer supported

14. type Book {
name: String
longName: String @deprecated(reason: "use name instead")
}

17. I love it 🤩
I want to create directives!

18. But why?

19. •Resolved server-side
→ less computation on client
•Most of GraphQL clients cache queries
→ avoid computation
•Declarative
→ understand code by reading query

20. query {
user {
name @upperCase
}
}
Text Formatting

21. Date Formatting
query {
user {
birthDate @dateFormat(format: "DD/MM/YYYY")
}
}

22. Restrictions
type User {
privateNote: String @requireAuth
}

23. Let's do it!

25. 😒

27. 🤔

29. 🤔🤔

31. 🤔🤔🤔

32. Sorry @leebyron 🤭

33. Behind a directive

34. /**
* Used to conditionally include fields or fragments.
*/
export const GraphQLIncludeDirective = new GraphQLDirective({
name: 'include',
description:
'Directs the executor to include this field or fragment only when ' +
'the `if` argument is true.',
locations: [
DirectiveLocation.FIELD,
DirectiveLocation.FRAGMENT_SPREAD,
DirectiveLocation.INLINE_FRAGMENT,
],
args: {
if: {
type: new GraphQLNonNull(GraphQLBoolean),
description: 'Included when true.',
},
},
})

35. /**
* The set of allowed directive location values.
*/
export const DirectiveLocation = {
// Request Definitions
QUERY: 'QUERY',
MUTATION: 'MUTATION',
SUBSCRIPTION: 'SUBSCRIPTION',
FIELD: 'FIELD',
FRAGMENT_DEFINITION: 'FRAGMENT_DEFINITION',
FRAGMENT_SPREAD: 'FRAGMENT_SPREAD',
INLINE_FRAGMENT: 'INLINE_FRAGMENT',
// Type System Definitions
SCHEMA: 'SCHEMA',
SCALAR: 'SCALAR',
OBJECT: 'OBJECT',
FIELD_DEFINITION: 'FIELD_DEFINITION',
ARGUMENT_DEFINITION: 'ARGUMENT_DEFINITION',
INTERFACE: 'INTERFACE',
UNION: 'UNION',
ENUM: 'ENUM',
ENUM_VALUE: 'ENUM_VALUE',
INPUT_OBJECT: 'INPUT_OBJECT',
INPUT_FIELD_DEFINITION: 'INPUT_FIELD_DEFINITION',
}

36. 🤩
We can put directive
everywhere!

37. How to declare a
directive?

38. # GraphQL Schema
directive @dateFormat(format: String!) on FIELD | FIELD_DEFINITION

39. How to use it?

41. I can use my own
directive 😎

43. But it doesn't work 😓

44. I need a directive
resolver!

45. Wait...

46. How to define a
directive resolver?

47. Not supported 😨

48. Let's take a look to a
resolver signature

50. Logging info...

51. { fieldName: 'birthDate',
fieldNodes:
[ { kind: 'Field',
alias: null,
name: [Object],
arguments: [],
directives: [Array],
selectionSet: null,
loc: [Object] } ],
returnType: DateTime,
parentType: Human,
path:
{ prev: { prev: undefined, key: 'character' },
key: 'birthDate' },
schema:
GraphQLSchema {
_queryType: Query,
_mutationType: Mutation,
_subscriptionType: Subscription,
_directives:
[ [GraphQLDirective],
[GraphQLDirective],
[GraphQLDirective],
[GraphQLDirective] ],
astNode:
{ kind: 'SchemaDefinition',
SPOTED

52. [ { kind: 'Directive',
name: { kind: 'Name', value: 'dateFormat', loc: [Object] },
arguments: [ [Object] ],
loc: { start: 37, end: 62 } } ]

53. Let's write a directive
resolver!

54. import format from 'date-fns/format'
const resolvers = {
Character: {
birthDate(obj, args, context, info) {
const directive = info.fieldNodes[0].directives.find(
directive => directive.name.value === 'dateFormat',
)
if (directive) {
const formatArg = directive.arguments.find(
arg => arg.name.value === 'format',
)
return formatDate(obj.birthDate, formatArg.value.value)
}
return obj.birthDate
},
}
}

56. I can use my own
directive and it works 😎

57. But it is not generic 😓

59. Introducing
graphql-directive

61. import { buildSchema } from 'graphql'
import { addDirectiveResolveFunctionsToSchema } from 'graphql-directive'
import format from 'date-fns/format'
// Schema
const schema = buildSchema(`
directive @dateFormat(format: String) on FIELD_DEFINITION | FIELD
`)
// Resolver
addDirectiveResolveFunctionsToSchema(schema, {
async dateFormat(resolve, source, args) {
const value = await resolve()
return format(new Date(value), args.format)
},
})

62. graphql-directive
•Easy to use
•Supports FIELD and FIELD_DEFINITION
locations
•Gives new power 🚀

63. Wait, I use it in my project
and it is random 🤔

64. The problem

65. query {
myField @upperCase
}
Query
Apollo Cache
{
"myField": "MYRESULT"
}
With directive
query {
myField
}
{
"myField": "myResult"
}
Without directive
Same result 😱

66. The fix

67. query {
myField @upperCase
}
Query
Apollo Cache
{
"myField@upperCase": "MYRESULT"
}
With directive
query {
myField
}
{
"myField": "myResult"
}
Without directive
Include directive
in cache key ✨

69. THANKS
I will tweet slides after the talk @neoziro