forked from apollographql/specs
-
Notifications
You must be signed in to change notification settings - Fork 0
/
nullability-v0.2.graphql
122 lines (94 loc) · 3.77 KB
/
nullability-v0.2.graphql
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
"""
Indicates that a position is semantically non null: it is only null if there is a matching error in the `errors` array.
In all other cases, the position is non-null.
Tools doing code generation may use this information to generate the position as non-null if field errors are handled out of band:
```graphql
type User {
# email is semantically non-null and can be generated as non-null by error-handling clients.
email: String @semanticNonNull
}
```
The `levels` argument indicates what levels are semantically non null in case of lists:
```graphql
type User {
# friends is semantically non null
friends: [User] @semanticNonNull # same as @semanticNonNull(levels: [0])
# every friends[k] is semantically non null
friends: [User] @semanticNonNull(levels: [1])
# friends as well as every friends[k] is semantically non null
friends: [User] @semanticNonNull(levels: [0, 1])
}
```
`levels` are zero indexed.
Passing a negative level or a level greater than the list dimension is an error.
"""
directive @semanticNonNull(levels: [Int] = [0]) on FIELD_DEFINITION
"""
Indicates that a position is semantically non null: it is only null if there is a matching error in the `errors` array.
In all other cases, the position is non-null.
`@semanticNonNullField` is the same as `@semanticNonNull` but can be used on type system extensions for services
that do not own the schema like client services:
```graphql
# extend the schema to make User.email semantically non-null.
extend type User @semanticNonNullField(name: "email")
```
The `levels` argument indicates what levels are semantically non null in case of lists:
```graphql
# friends is semantically non null
extend type User @semanticNonNullField(name: "friends") # same as @semanticNonNullField(name: "friends", levels: [0])
# every friends[k] is semantically non null
extend type User @semanticNonNullField(name: "friends", levels: [1])
# friends as well as every friends[k] is semantically non null
extend type User @semanticNonNullField(name: "friends", levels: [0, 1])
```
`levels` are zero indexed.
Passing a negative level or a level greater than the list dimension is an error.
See `@semanticNonNull`.
"""
directive @semanticNonNullField(name: String!, levels: [Int] = [0]) repeatable on OBJECT | INTERFACE
"""
Indicates how clients should handle errors on a given position.
When used on the schema definition, `@catch` applies to every position that can return an error.
The `levels` argument indicates where to catch errors in case of lists:
```graphql
{
user {
# friends catches errors
friends @catch { name } # same as @catch(levels: [0])
# every friends[k] catches errors
friends @catch(levels: [0]) { name }
# friends as well as every friends[k] catches errors
friends @catch(levels: [0, 1]) { name }
}
}
```
`levels` are zero indexed.
Passing a negative level or a level greater than the list dimension is an error.
See `CatchTo` for more details.
"""
directive @catch(to: CatchTo! = RESULT, levels: [Int] = [0]) on FIELD | SCHEMA
enum CatchTo {
"""
Catch the error and map the position to a result type that can contain either
a value or an error.
"""
RESULT,
"""
Catch the error and map the position to a nullable type that will be null
in the case of error.
This does not allow to distinguish between semantic null and error null but
can be simpler in some cases.
"""
NULL,
"""
Throw the error.
Parent positions can recover using `RESULT` or `NULL`.
If no parent position recovers, the parsing stops.
"""
THROW
}
"""
Never throw on field errors.
This is used for backward compatibility for clients where this was the default behaviour.
"""
directive @ignoreErrors on QUERY | MUTATION | SUBSCRIPTION