From 07c77ead7425f1877372d358d867445a4c525c96 Mon Sep 17 00:00:00 2001
From: Diego Imbert <70353967+diegoimbert@users.noreply.github.com>
Date: Wed, 26 Aug 2026 00:48:28 +0200
Subject: [PATCH] feat(frontend): flag the fork-compare datatable schema diff
 as legacy (#10829)

* feat(frontend): flag the fork-compare datatable schema diff as legacy

* fix(frontend): make the legacy datatable diff alert copy match the opt-in flag
---
 frontend/src/lib/components/DatatableSchemaDiff.svelte | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/frontend/src/lib/components/DatatableSchemaDiff.svelte b/frontend/src/lib/components/DatatableSchemaDiff.svelte
index 579b7a1923..1fb6918580 100644
--- a/frontend/src/lib/components/DatatableSchemaDiff.svelte
+++ b/frontend/src/lib/components/DatatableSchemaDiff.svelte
@@ -48,6 +48,9 @@
 	// migrations, its changes flow through the normal item diff instead, so it is
 	// excluded here and the whole section hides once none remain.
 	let applicableCount = $state(0)
+	let applicableLabel = $derived(
+		applicableCount === 1 ? 'this data table has' : 'these data tables have'
+	)
 	let expandedDatatables: Set<string> = $state(new Set())
 
 	// Drawer state
@@ -293,6 +296,12 @@
 {#if applicableCount > 0}
 	<div class="bg-surface-tertiary p-4 rounded-md border">
 		<h3 class="text-sm font-semibold">Datatable schema changes</h3>
+		<Alert type="warning" size="xs" title="Legacy schema comparison" class="mt-2">
+			This section diffs data table schemas directly because {applicableLabel} not opted in to migrations.
+			With migrations enabled, schema changes are tracked as migrations and deployed like any other item.
+			Opt in from the parent workspace's data table settings — a fork only inherits the flag when it
+			is created, so this fork keeps using the legacy diff.
+		</Alert>
 		{#if loading}
 			<div class="flex items-center gap-2 text-xs text-tertiary py-2">
 				<Loader2 class="w-4 h-4 animate-spin" /> Loading datatable diffs...