From b244f831dad8ab7f43d3e7f17c0c4249c05a9358 Mon Sep 17 00:00:00 2001
From: Philipinho <16838612+Philipinho@users.noreply.github.com>
Date: Sat, 18 Apr 2026 13:29:32 +0100
Subject: [PATCH] refactor(base): drop type-change invalidation branch from
 update-property mutation

---
 .../src/features/base/queries/base-property-query.ts | 12 ------------
 1 file changed, 12 deletions(-)

diff --git a/apps/client/src/features/base/queries/base-property-query.ts b/apps/client/src/features/base/queries/base-property-query.ts
index f1ad8acb..0d44efa3 100644
--- a/apps/client/src/features/base/queries/base-property-query.ts
+++ b/apps/client/src/features/base/queries/base-property-query.ts
@@ -62,18 +62,6 @@ export function useUpdatePropertyMutation() {
           };
         },
       );
-
-      // Invalidate rows only for the synchronous (inline) path — the
-      // HTTP response there is the "cells are migrated" signal. When the
-      // server hands back a `jobId`, cells are still being rewritten; the
-      // `base:schema:bumped` socket event is the canonical refetch
-      // trigger in that case, and we'd only churn pages with old data by
-      // refetching now.
-      if (variables.type && !result.jobId) {
-        queryClient.invalidateQueries({
-          queryKey: ["base-rows", variables.baseId],
-        });
-      }
     },
     onError: () => {
       notifications.show({