Skip to content

Update solution 6. #1708

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.

Sign up for GitHub

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

Merged
benjie merged 5 commits into from
Mar 29, 2025
Merged

Update solution 6. #1708

Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
4163bf9
Update solution 6.
martinbonnin Mar 28, 2025
886b24e
Update rfcs/SemanticNullability.md
martinbonnin Mar 28, 2025
5ba2be6
Update rfcs/SemanticNullability.md
martinbonnin Mar 28, 2025
ad2b10f
Update rfcs/SemanticNullability.md
martinbonnin Mar 28, 2025
3cd250c
add benjie as champion
martinbonnin Mar 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 9 additions & 4 deletions rfcs/SemanticNullability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -940,13 +940,18 @@ This proposal relies on the ability of clients to opt out of error propagation;

[solution-6]: #-6-semanticnonnull-directive

**Champion**: -
**Champion**: @benjie

Outline: https://specs.apollo.dev/nullability/v0.4/#@semanticNonNull

This proposal (which is already adopted in a few places!) introduces a
directive that can be added to fields to indicate their semantic nullability
(and that of their nested list positions).
This proposal relies on:
- A new directive, `@semanticNonNull`
- Either:
- A new introspection argument, `includeSemanticNonNull` (`__Field.type(includeSemanticNonNull: Boolean! = false)`), if represented as a type, or
- A new introspection field, `__Field.semanticNonNullLevels: [Int!]`, if represented as field metadata

The directive (which is already adopted in a few places!) can be added to
fields to indicate their semantic nullability (and that of their nested list positions).

```graphql
directive @semanticNonNull(levels: [Int!]! = [0]) on FIELD_DEFINITION
Expand Down