fix: invalidate OMO Slim query cache after provider mutations

OMO Slim queries (["omo-slim", ...]) were not invalidated alongside
OMO queries, causing stale UI state when switching/adding/deleting
OMO Slim providers.
This commit is contained in:
Jason
2026-02-26 17:51:50 +08:00
parent 3e2c8c12a5
commit 55e21c3c19
+15
View File
@@ -57,6 +57,12 @@ export const useAddProviderMutation = (appId: AppId) => {
await queryClient.invalidateQueries({
queryKey: ["omo", "provider-count"],
});
await queryClient.invalidateQueries({
queryKey: ["omo-slim", "current-provider-id"],
});
await queryClient.invalidateQueries({
queryKey: ["omo-slim", "provider-count"],
});
}
try {
@@ -139,6 +145,12 @@ export const useDeleteProviderMutation = (appId: AppId) => {
await queryClient.invalidateQueries({
queryKey: ["omo", "provider-count"],
});
await queryClient.invalidateQueries({
queryKey: ["omo-slim", "current-provider-id"],
});
await queryClient.invalidateQueries({
queryKey: ["omo-slim", "provider-count"],
});
}
try {
@@ -190,6 +202,9 @@ export const useSwitchProviderMutation = (appId: AppId) => {
await queryClient.invalidateQueries({
queryKey: ["omo", "current-provider-id"],
});
await queryClient.invalidateQueries({
queryKey: ["omo-slim", "current-provider-id"],
});
}
if (appId === "openclaw") {
await queryClient.invalidateQueries({