Back to Signal Feed
CodeTracked since May 19, 2026

Persist DataGrid column order via localStorage

The PR adds persistent column reordering for `DataGrid` by introducing a `useColumnOrder` hook and an optional `storageKey` prop, so reordered columns are saved to `localStorage`, validated on restore, and reapplied after reloads while preserving current defaults when storage is unavailable.

DataGridlocalStoragestorageKeyuseColumnOrder

What Happened

  • The PR adds persistent column reordering for `DataGrid` by introducing a `useColumnOrder` hook and an optional `storageKey` prop, so reordered columns are saved to `localStorage`, validated on restore, and reapplied after reloads while preserving current defaults when storage is unavailable.
  • The PR adds persistent column reordering for `DataGrid` by introducing a `useColumnOrder` hook and an optional `storageKey` prop, so reordered columns are saved to `localStorage`, validated on restore, and reapplied after reloads while preserving current defaults when storage is unavailable.
  • 1 evidence item attached for review.

What is Different

Before

Scattered source updates, isolated context, and manual follow-up across multiple feeds.

Now

Added persistent column ordering support to `DataGrid` through a new `useColumnOrder` hook that stores and restores drag-and-drop column order in `localStorage` and safely handles invalid or stale saved orders by normalizing against current columns and defaulting when needed.

Why Track This

Why It Matters

Users working in InsForge tables will keep their custom column layout after refresh, which reduces repeated manual reconfiguration and makes repeated review/analysis sessions faster and less error-prone; teams should monitor whether order persistence degrades when browser storage is cleared, unavailable, or contains outdated/malformed entries because the grid may revert to a default layout. Technically, this is implemented with a configurable `storageKey`, a reorder persistence path in `onColumnsReorder`, and key validation during restore.

Impact

Users working in InsForge tables will keep their custom column layout after refresh, which reduces repeated manual reconfiguration and makes repeated review/analysis sessions faster and less error-prone; teams should monitor whether order persistence degrades when browser storage is cleared, unavailable, or contains outdated/malformed entries because the grid may revert to a default layout. Technically, this is implemented with a configurable `storageKey`, a reorder persistence path in `onColumnsReorder`, and key validation during restore.

What To Watch Next

  • Watch whether DataGrid becomes a repeated pattern.
  • Track follow-up changes around AI Integration in IDEs.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: stale_or_malformed_storage_keys, localstorage_unavailable_fallback_to_default.
Open Topic TimelineOpen Technical EventOpen Original Sourcestale_or_malformed_storage_keys / localstorage_unavailable_fallback_to_default / storagekey_collision_across_tables

Supporting Evidence

GITHUB PULL REQUESTHigh Trust

InsForge/InsForge PR #1296: feat: add persistent column re-ordering with localStorage

A new `storageKey` enables drag-reordered column keys to be persisted in `localStorage`; a new hook reads/writes and validates this order, appends missing columns on schema changes, and falls back to the default order on invalid storage state.