fix(types): adapt type definition of dataOrUpdater in setQueryData (#540

) since the updater receives `T | undefined`, it is difficult to construct a `T` from that. oldData can legitimately be `undefined`, but since `getQueryData` can also return `undefined` at any point, it makes more sense to have the updater be able to return `undefined` as well, which also means that `data` itself can be `undefined`
TanStack · Jun 2, 2020 · b528564 · b528564
1 parent 3a589bb
commit b528564
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/types/index.d.ts b/types/index.d.ts
@@ -604,7 +604,7 @@ export interface CachedQuery<T, TError = unknown> {
   config: QueryOptions<unknown, TError>
   state: CachedQueryState<T>
   setData(
-    dataOrUpdater: unknown | ((oldData: unknown | undefined) => unknown)
+    dataOrUpdater: unknown | undefined | ((oldData: unknown | undefined) => unknown | undefined)
   ): void
   clear(): void
 }
@@ -686,7 +686,7 @@ export interface QueryCache {
   getQueryData<T = unknown>(key: AnyQueryKey | string): T | undefined
   setQueryData<T = unknown>(
     key: AnyQueryKey | string,
-    dataOrUpdater: T | ((oldData: T | undefined) => T)
+    dataOrUpdater: T | undefined | ((oldData: T | undefined) => T | undefined)
   ): void
   refetchQueries<TResult>(
     queryKeyOrPredicateFn: