Semantic Nullability - A Path Toward Safe NonNull Fields

on YouTube ↗31m

" summary

Proposes decoupling GraphQL nulls from execution errors so clients see only semantic nulls and servers retain response resilience, implemented with a userland catch directive plus throw on field error behavior that lets React error boundaries contain failures. Relay 18 ships these features; Apollo, Caliban and grz add support and a Benji pre‑RFC explores standardizing it. Clients generate non‑nullable types when errors are handled, reducing null checks while preserving error metadata; production validation and forward‑compatibility questions remain.

AI-written summary · about

" chapters (8)

1. 0:00Introduction to talk
2. 2:34Nullability and errors in GraphQL
3. 7:31Client-side error handling
4. 11:02Semantic non-null fields
5. 14:33Recap and benefits
6. 16:37Current implementations
7. 18:22Future of semantic non-null
8. 19:47Q&A session

" related talks

• 29mFixing the Billion Dollar Mistake Client Controlled NullabilityStephen Spalding · GraphQLConf 2023
• 23mImproving User Experiences with a Nullable SchemaErnie Turner · GraphQLConf 2023
• 47mRock-Solid Components with TypeScript and GraphQLMat Warger · NDC Porto 2019
• 21mHow not to break GraphQL clients?Suraj Chafle · GraphQL Conf. 2022
• 35mFull-stack Type Safety with React, GraphQL, and TypeScriptRobert Zhu · React Boston 2019
• 32mFrom learning to thinking in GraphQLGlenn Reyes · FrontEnd Con 2018
• 26mFull Stack Type Safety with React, GraphQL, and TypeScriptRobert Zhu · Nordic.js 2019
• 25mType-safe GraphQL with TypeScriptAaron Powell · OpenJS World 2021