bring back the old errors to error behavior in useQuery

apollographql · Aug 6, 2021 · 644f623 · 644f623
1 parent 5ce8bb9
commit 644f623
Showing 1 changed file with 8 additions and 0 deletions.
diff --git a/src/react/hooks/useQuery.ts b/src/react/hooks/useQuery.ts
@@ -327,6 +327,14 @@ export function useQuery<
       error: void 0,
       networkStatus: NetworkStatus.ready,
     };
+  } else if (result.errors && result.errors.length) {
+    // Until a set naming convention for networkError and graphQLErrors is
+    // decided upon, we map errors (graphQLErrors) to the error options.
+    // TODO: Is it possible for both result.error and result.errors to be defined here?
+    result = {
+      ...result,
+      error: result.error || new ApolloError({ graphQLErrors: result.errors }),
+    };
   }
 
   // TODO: Is this still necessary?