useFetch: Fix mapResult being required when not using paginated o…

…verload.
raycast · Mar 18, 2024 · 728c8d2 · 728c8d2
1 parent 568324c
commit 728c8d2
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 4 deletions.
diff --git a/docs/utils-reference/getting-started.md b/docs/utils-reference/getting-started.md
@@ -19,6 +19,7 @@ npm install --save @raycast/utils
 ### v1.13.3
 
 - Fixed `optimisticUpdate` not working when paginating beyond the first page when using `useCachedPromise` or other hooks that build on top of it..
+- Fixed `useFetch` type requiring `mapResult` for non-paginated overload.
 
 ### v1.13.2
 
@@ -34,12 +35,12 @@ npm install --save @raycast/utils
 
 ### v1.12.5
 
-- Added string array support for OAuth scope (Thanks @tonka3000!).
+- Add string array support for OAuth scope (Thanks @tonka3000!).
 
 ### v1.12.4
 
-- Added `tokenResponseParser` and `tokenRefreshResponseParser` in the options of `OAuthService`.
-- Fixed built-in Slack OAuthServices.
+- Add `tokenResponseParser` and `tokenRefreshResponseParser` in the options of `OAuthService`.
+- Fix built-in Slack OAuthServices.
 
 ### v1.12.3
 

diff --git a/src/useFetch.ts b/src/useFetch.ts
@@ -131,7 +131,7 @@ export function useFetch<V = unknown, U = undefined, T extends unknown[] = unkno
 export function useFetch<V = unknown, U = undefined, T = V>(
   url: RequestInfo,
   options?: RequestInit & {
-    mapResult: (result: V) => { data: T; hasMore?: boolean };
+    mapResult?: (result: V) => { data: T; hasMore?: boolean };
     parseResponse?: (response: Response) => Promise<V>;
   } & Omit<CachedPromiseOptions<(url: RequestInfo, options?: RequestInit) => Promise<T>, U>, "abortable">,
 ): UseCachedPromiseReturnType<T, U> & { pagination: undefined };