LumeWeb
/
portal-dashboard
1
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity

fix: add extra invalidate after pinning and unpinning request

This commit is contained in:
Juan Di Toro 2024-03-27 07:53:51 +01:00
parent af9acd1bf7
commit 810948242f
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
app/hooks/usePinning.ts
View File

@ -1,4 +1,4 @@
import { useNotification } from "@refinedev/core";
import { useInvalidate, useNotification } from "@refinedev/core";
import { useMutation, useQueryClient } from "@tanstack/react-query";
import { useCallback, useContext } from "react";
import { PinningProcess } from "~/data/pinning";
@ -6,6 +6,7 @@ import { PinningContext } from "~/providers/PinningProvider";
export const usePinning = () => {
const queryClient = useQueryClient();
const invalidate = useInvalidate();
const context = useContext(PinningContext);
const { open } = useNotification();
@ -25,6 +26,7 @@ export const usePinning = () => {
}
queryClient.invalidateQueries({ queryKey: ["pin-progress", "file"] });
invalidate({ resource: "file", invalidates: ["list"] });
return Promise.resolve(response);
},
});
@ -44,6 +46,7 @@ export const usePinning = () => {
return Promise.reject(response);
}
queryClient.invalidateQueries({ queryKey: ["pin-progress"] });
invalidate({ resource: "file", invalidates: ["list"] });
return Promise.resolve(response);
},
});