Back to Signal Feed
CodeTracked since May 19, 2026

Persist DataGrid column order across page reloads

Adds persistent column reordering for InsForge `DataGrid`, saving drag-and-drop order in local storage per table and restoring it on reload while keeping default behavior when persistence is not enabled.

DataGridlocalStorageuseColumnOrderstorageKey

What Happened

  • Adds persistent column reordering for InsForge `DataGrid`, saving drag-and-drop order in local storage per table and restoring it on reload while keeping default behavior when persistence is not enabled.
  • Adds persistent column reordering for InsForge `DataGrid`, saving drag-and-drop order in local storage per table and restoring it on reload while keeping default behavior when persistence is not enabled.
  • 1 evidence item attached for review.

What is Different

Before

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

Now

Implemented a new optional persistence path for column ordering: `DataGrid` now accepts a `storageKey` and uses a `useColumnOrder` hook to read/write ordered column keys in localStorage, validate stored keys, append missing keys after schema changes, and persist reorder events. It also fixes a reorder splice off-by-one edge case in the same flow.

Why Track This

Why It Matters

Users configuring table views will keep their preferred column layout after refreshing the page, so they spend less time reordering columns before doing data work, while developers can enable stable, per-view behavior by setting `storageKey` on each grid. The implementation now restores or safely resets order based on validated stored state, so operators should watch for malformed or stale localStorage values and storage failures (such as private-browser restrictions or quota limits) that can silently force a fallback to default ordering.

Impact

Users configuring table views will keep their preferred column layout after refreshing the page, so they spend less time reordering columns before doing data work, while developers can enable stable, per-view behavior by setting `storageKey` on each grid. The implementation now restores or safely resets order based on validated stored state, so operators should watch for malformed or stale localStorage values and storage failures (such as private-browser restrictions or quota limits) that can silently force a fallback to default ordering.

What To Watch Next

  • Watch whether DataGrid becomes a repeated pattern.
  • Track follow-up changes around AI IDE.
  • Compare future signals against this evidence trail.
  • Re-check risk flags: invalid_localstorage_payloads, localstorage_access_errors.
Open Topic TimelineOpen Technical EventOpen Original Sourceinvalid_localstorage_payloads / localstorage_access_errors / stored_order_mismatch_with_schema_changes

Supporting Evidence