fix(tables): key-order-stable dirty check, reset layout when switching to All

Author: TheodoreSpeaks

apps/sim/app/workspace/[workspaceId]/tables/[tableId]/components/table-grid/table-grid.tsx

@@ -1759,20 +1759,22 @@ export function TableGrid({
     // With a view active its config owns the layout; otherwise the table's own
     // metadata does. Switching views re-seeds unconditionally so the incoming
     // view's layout replaces the outgoing one.
-    const source = viewLayout ?? tableData?.metadata
+    const source = viewLayout ?? tableData?.metadata ?? null
     const switchedView = viewLayoutKey !== seededLayoutKeyRef.current
-    if (!source) return
-    if (!source.columnWidths && !source.columnOrder && !source.pinnedColumns && !switchedView)
-      return
 
     if (!metadataSeededRef.current || switchedView) {
+      // A switch resets even when there is nothing to seed from — a table created
+      // with `metadata: null` would otherwise keep showing the outgoing view's
+      // layout, since layout written under a view never populates table metadata.
+      if (!source && !switchedView) return
       metadataSeededRef.current = true
       seededLayoutKeyRef.current = viewLayoutKey
-      setColumnWidths(source.columnWidths ?? {})
-      setColumnOrder(source.columnOrder ?? null)
-      setPinnedColumns(source.pinnedColumns ?? [])
+      setColumnWidths(source?.columnWidths ?? {})
+      setColumnOrder(source?.columnOrder ?? null)
+      setPinnedColumns(source?.pinnedColumns ?? [])
       return
     }
+    if (!source) return
     // After first load: only re-seed `columnOrder` when the *set of columns*
     // changes (e.g. a workflow group adds/removes outputs server-side). Pure
     // reorders are left alone so an in-flight optimistic drag isn't clobbered

apps/sim/app/workspace/[workspaceId]/tables/[tableId]/table.tsx

@@ -141,18 +141,33 @@ const NO_VIEWS: TableViewWire[] = []
 
 type ViewModalState = { mode: 'create' } | { mode: 'rename'; viewId: string } | null
 
+/**
+ * Order-insensitive JSON, used to compare a locally-built config against one that
+ * has round-tripped through Postgres. `jsonb` does not preserve object key order
+ * (`{status,plan}` comes back `{plan,status}`), so a plain `JSON.stringify` would
+ * report any multi-key filter as permanently dirty. Array order is preserved —
+ * it is meaningful for `columnOrder`.
+ */
+function stableStringify(value: unknown): string {
+  if (value === null || typeof value !== 'object') return JSON.stringify(value) ?? 'null'
+  if (Array.isArray(value)) return `[${value.map(stableStringify).join(',')}]`
+  const entries = Object.entries(value as Record<string, unknown>)
+    .filter(([, entry]) => entry !== undefined)
+    .sort(([left], [right]) => (left < right ? -1 : left > right ? 1 : 0))
+  return `{${entries.map(([key, entry]) => `${JSON.stringify(key)}:${stableStringify(entry)}`).join(',')}}`
+}
+
 /**
  * Structural equality for the parts of a view config the user edits directly.
  * Column layout (widths/order/pinning) is excluded — it auto-saves into the
  * active view as the user drags, so it can never be the thing that is "unsaved".
  *
- * Compares JSON rather than field-by-field because `filter` is an arbitrarily
- * nested predicate tree; key order is stable since both sides are built by the
- * same converters.
+ * Compares serialized form rather than field-by-field because `filter` is an
+ * arbitrarily nested predicate tree.
  */
 function isSameViewConfig(a: TableViewConfig, b: TableViewConfig): boolean {
   const normalize = (config: TableViewConfig) =>
-    JSON.stringify({
+    stableStringify({
       filter: config.filter ?? null,
       sort: config.sort ?? null,
       hiddenColumns: [...(config.hiddenColumns ?? [])].sort(),