extract handleApiError

packages/commerce-sdk-react/src/hooks/useQuery.ts

@@ -16,7 +16,7 @@ import {
     NullableParameters,
     OmitNullableParameters
 } from './types'
-import {hasAllKeys} from './utils'
+import {hasAllKeys, handleApiError} from './utils'
 import {onClient} from '../utils'
 
 /**
@@ -48,16 +48,10 @@ export const useQuery = <Client extends ApiClient, Options extends ApiOptions, D
     // missing parameters. This will result in a runtime error. I think that this is an acceptable
     // trade-off, as the behavior is opt-in by the end user, and it feels like adding type safety
     // for this case would add significantly more complexity.
-    const wrappedMethod = async () => {
-        try {
-            return await authenticatedMethod(apiOptions as Options)
-        } catch (e) {
-            if (typeof e === 'object' && e !== null && 'response' in e) {
-                const json = await (e.response as Response).json()
-                throw json
-            }
-            throw e
-        }
+    const wrappedMethod = () => {
+        return handleApiError(() => {
+            return authenticatedMethod(apiOptions as Options)
+        })
     }
     return useReactQuery(hookConfig.queryKey, wrappedMethod, {
         enabled:

packages/commerce-sdk-react/src/hooks/utils.ts

@@ -138,3 +138,15 @@ export const getCustomKeys = <T extends object>(obj: T) => {
     }
     return Object.keys(obj).filter((key: string): key is `c_${string}` => key.startsWith('c_'))
 }
+
+export const handleApiError = async <T>(func: () => Promise<T>): Promise<T> => {
+    try {
+        return await func()
+    } catch (e) {
+        if (typeof e === 'object' && e !== null && 'response' in e) {
+            const json = await (e.response as Response).json()
+            throw json
+        }
+        throw e
+    }
+}