Fixing the Billion Dollar Mistake Client Controlled Nullability
summary
GraphQL gains a proposal that moves nullability control from server schema into the query: a client-side operator (a client-side bang) flips bubbling behavior so a field can be treated non-null by the client, a query-level question mark opts a schema non-null into client-handled nullable, and a try/catch-style bubble stops at the nearest marked ancestor. Prototypes exist inside Netflix Yelp and Facebook and an RFC lives in the working group since 2021; implementations and client library support are required to validate real-world behavior.
AI-written summary · about
chapters (8)
- 0:00The problem with nulls
- 2:20GraphQL nullability basics
- 7:17Client-controlled nullability
- 10:07History of null handling
- 14:37Developing the proposal
- 18:28Advanced null techniques
- 22:23Defining true nullability
- 26:07Future and call to action
related talks
31mSemantic Nullability - A Path Toward Safe NonNull Fields
32mThe Billion D∅Llar Panel - Nullability in GraphQL
10mUNSET Fields: Contrasting Null and Purposeful Omissions in Server Response
21mHow not to break GraphQL clients?
25mWhat's next for GraphQL?
32mHow to Not Break Your GraphQL Clients
30mWhy GraphQL vs. Why not GraphQL
32mFrom learning to thinking in GraphQL