kitten.sh
commits
The ["Nullability RFC" for GraphQL](https://github.com/graphql/graphql-wg/issues/694)
allows fields to individually be marked as optional or required in a query by the
client-side. ([See Strawman Proposal](https://github.com/graphql/graphql-spec/issues/867))
If a field is marked as optional then it's allowed to be missing and `null`, which
can control where missing values cascade to:
```graphql
query {
me {
name?
}
}
```
If a field is marked as required it may never be allowed to become `null` and must
cascade if it otherwise would have been set to `null`:
```graphql
query {
me {
name!
}
}
```
* Switch to graphql@16 alpha
* prepare size check
* add command
* only compare vendor
* formatting
* convert to preact
Co-authored-by: Phil Pluckthun <phil@kitten.sh>
The ["Nullability RFC" for GraphQL](https://github.com/graphql/graphql-wg/issues/694)
allows fields to individually be marked as optional or required in a query by the
client-side. ([See Strawman Proposal](https://github.com/graphql/graphql-spec/issues/867))
If a field is marked as optional then it's allowed to be missing and `null`, which
can control where missing values cascade to:
```graphql
query {
me {
name?
}
}
```
If a field is marked as required it may never be allowed to become `null` and must
cascade if it otherwise would have been set to `null`:
```graphql
query {
me {
name!
}
}
```