Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add nullability directives #36

Merged
merged 13 commits into from
Dec 11, 2023
5 changes: 3 additions & 2 deletions __index__.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,9 @@
- **[join/v0.1](/join/v0.1)** ([📄 graphql](join/v0.1/join-v0.1.graphql))
- **[join/v0.2](/join/v0.2)** ([📄 graphql](join/v0.2/join-v0.2.graphql))
- **[join/v0.3](/join/v0.3)** ([📄 graphql](join/v0.3/join-v0.3.graphql))
- **[kotlin_labs/v0.1](/kotlin_labs/v0.1)** ([📄 graphql](kotlin_labs/v0.1/kotlin_labs-v0.1.graphql))
- **[kotlin_labs/v0.2](/kotlin_labs/v0.2)** ([📄 graphql](kotlin_labs/v0.2/kotlin_labs-v0.2.graphql))
- **[link/v1.0](/link/v1.0)** ([📄 graphql](link/v1.0/link-v1.0.graphql))
- **[nullability/v0.1](/nullability/v0.1)** ([📄 graphql](nullability/v0.1/nullability-v0.1.graphql))
- **[tag/v0.1](/tag/v0.1)** ([📄 graphql](tag/v0.1/tag-v0.1.graphql))
- **[tag/v0.2](/tag/v0.2)** ([📄 graphql](tag/v0.2/tag-v0.2.graphql))
- **[kotlin_labs/v0.1](/kotlin_labs/v0.1)** ([📄 graphql](kotlin_labs/v0.1/kotlin_labs-v0.1.graphql))
- **[kotlin_labs/v0.2](/kotlin_labs/v0.2)** ([📄 graphql](kotlin_labs/v0.2/kotlin_labs-v0.2.graphql))
4 changes: 4 additions & 0 deletions index.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,10 @@

[kotlin_labs v0.2](kotlin_labs/v0.2) incubating directives supported by the Apollo Kotlin client

## nullability v0.1

[nullability v0.1](nullability/v0.1) incubating directives to work with nullability

# All Schemas

Everything in this library:
Expand Down
80 changes: 80 additions & 0 deletions nullability/v0.1/nullability-v0.1.graphql
Original file line number Diff line number Diff line change
@@ -0,0 +1,80 @@
"""
Indicates that a field is only null if there is a matching error in the `errors` array.
In all other cases, the field is non-null.

Tools doing code generation may use this information to generate the field as non-null.

This directive can be applied on field definitions:

```graphql
type User {
email: String @semanticNonNull
}
```

It can also be applied on object type extensions for use in client applications that do
not own the base schema:

```graphql
extend type User @semanticNonNull(field: "email")
```

Control over list items is done using the `level` argument:

```graphql
type User {
# friends is nullable but friends[0] is null only on errors
friends: [User] @semanticNonNull(level: 1)
}
```

The `field` argument is the name of the field if `@semanticNonNull` is applied to an object definition.
If `@semanticNonNull` is applied to a field definition, `field` must be null.

The `level` argument can be used to indicate what level is semantically non null in case of lists.
`level` starts at 0 if there is no list. If `level` is null, all levels are semantically non null.
"""
directive @semanticNonNull(field: String = null, level: Int = null) repeatable on FIELD_DEFINITION | OBJECT

"""
Indicates that the given position stops GraphQL errors to propagate up the tree.

By default, the first GraphQL error stops the parsing and fails the whole response.
Using `@catch` recovers from this error and allows the parsing to continue.

`@catch` can be used on the schema definition. In this case, it is the default for
every field that can return an error (nullable fields).
If no `@catch` is applied to the schema definition, errors are not
caught by default and the parsing stops at the first error.

The `to` argument can be used to choose how to recover from errors. See `CatchTo`
for more details.

The `level` argument can be used to indicate where to catch in case of lists.
`level` starts at 0 if there is no list. If `level` is null, all levels catch.
"""
directive @catch(to: CatchTo! = RESULT, level: Int = null) repeatable on FIELD | SCHEMA

enum CatchTo {
"""
Map to a result type that can contain either a value or an error.
"""
RESULT,
BoD marked this conversation as resolved.
Show resolved Hide resolved
"""
Map to a nullable type that will be null in the case of error.
This does not allow to distinguish between semantic null and error but
can be simpler in some cases.
"""
NULL,
"""
Do not catch and let any exception through
"""
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
27 changes: 27 additions & 0 deletions nullability/v0.1/nullability-v0.1.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,27 @@
# nullability v0.1

<h2>Experimental nullability directives</h2>

```raw html
<table class=spec-data>
<tr><td>Status</td><td>Release</td>
<tr><td>Version</td><td>0.1</td>
</table>
<link rel=stylesheet href=https://specs.apollo.dev/apollo-light.css>
<script type=module async defer src=https://specs.apollo.dev/inject-logo.js></script>
```

This specification provides a list of directives to help dealing with nullability. For more information, see [the nullability working group GitHub](https://github.com/graphql/nullability-wg)


#! @semanticNonNull

:::[definition](nullability-v0.1.graphql#@semanticNonNull)

#! @catch

:::[definition](nullability-v0.1.graphql#@catch)

#! @ignoreFieldErrors

:::[definition](nullability-v0.1.graphql#@ignoreFieldErrors)
martinbonnin marked this conversation as resolved.
Show resolved Hide resolved