You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* @description Options related to handling nullability
298
298
* @exampleMarkdown
299
299
* ## `errorHandlingClient`
300
+
* An error handling client is a client which prevents the user from reading a `null` used as a placeholder for an error in a GraphQL response.
301
+
* The client may do so by throwing when an errored field is accessed (as is the case for [`graphql-toe`](https://github.com/graphile/graphql-toe)),
302
+
* or when a fragment containing an error is read (as is the case for Relay's `@throwOnFieldError` directive),
303
+
* or by preventing any data from being read if an error occurred (as with Apollo Client's `errorPolicy: "none"`).
304
+
*
300
305
* When using error handling clients, a semantic non-nullable field can never be `null`.
301
-
* If a field is read and its value is `null`, there must be a respective error. The error handling client will throw in this case, so the `null` value is never read.
306
+
* If a semantic non-nullable field's value in the response is `null`, there must be a respective error.
307
+
* The error handling client will throw in this case, so the `null` value is never read.
302
308
*
303
309
* To enable this option, install `graphql-sock` peer dependency:
0 commit comments