Update packages/plugins/typescript/operations/src/config.ts

benjie · eddeee888 · web-flow · commit ebab71a9b9fc · 2025-03-26T12:46:17.000Z
Co-authored-by: Eddy Nguyen &lt;github@eddeee888.me&gt;
diff --git a/packages/plugins/typescript/operations/src/config.ts b/packages/plugins/typescript/operations/src/config.ts
@@ -300,7 +300,7 @@ export interface TypeScriptDocumentsPluginConfig extends RawDocumentsConfig {
    * 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.
    * The client may do so by throwing when an errored field is accessed (as is the case for `graphql-toe`),
    * or when a fragment containing an error is read (as is the case for Relay's `@throwOnFieldError` directive),
-   * or by preventing any data from being read if an error occurred (as with Apollo's `errorPolicy: "none"`).
+   * or by preventing any data from being read if an error occurred (as with Apollo Client's `errorPolicy: "none"`).
    *
    * When using error handling clients, a semantic non-nullable field can never be `null`.
    * If a semantic non-nullable field's value in the response is `null`, there must be a respective error.

Original file line number	Diff line number	Diff line change
`@@ -300,7 +300,7 @@ export interface TypeScriptDocumentsPluginConfig extends RawDocumentsConfig {`
`300`	`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`	`301`	* The client may do so by throwing when an errored field is accessed (as is the case for `graphql-toe`),
`302`	`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's `errorPolicy: "none"`).
	`303`	+ * or by preventing any data from being read if an error occurred (as with Apollo Client's `errorPolicy: "none"`).
`304`	`304`	`*`
`305`	`305`	* When using error handling clients, a semantic non-nullable field can never be `null`.
`306`	`306`	* If a semantic non-nullable field's value in the response is `null`, there must be a respective error.