Skip to content

DataTables: persist grid state (page/length/search/order) house-wide - #133

Merged
WebTigers merged 1 commit into
mainfrom
fix/datatable-statesave
Aug 17, 2026
Merged

DataTables: persist grid state (page/length/search/order) house-wide#133
WebTigers merged 1 commit into
mainfrom
fix/datatable-statesave

Conversation

@WebTigers

Copy link
Copy Markdown
Owner

Grids weren't remembering page number, page length, search, or ordering across reloads/navigation.

The shared tigerDataTable helper never enabled DataTables' stateSave. Turned it on in the one wrapper so every admin grid (Users, Orgs, Code, CMS, Media, Skills) persists its state consistently — saved to localStorage, keyed by table id + path, stateDuration: 0 (kept until the user changes it, no time-based expiry). A caller can opt out with stateSave: false (caller opts win over the defaults).

View/asset-only change; deployed to tiger-dev (the asset() cache-bust picks up the new file mtime — a hard refresh once if the old JS is cached).

🤖 Generated with Claude Code

The shared tigerDataTable helper didn't enable stateSave, so every admin grid
forgot its page, page-length, search, and ordering on reload/navigation. Turn
on stateSave (localStorage, keyed by table id + path) with stateDuration 0
(keep until changed). House-wide: Users, Orgs, Code, CMS, Media, Skills all
remember where you were. A caller can opt out with stateSave:false.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@WebTigers
WebTigers merged commit 68e5bc9 into main Aug 17, 2026
13 checks passed
@WebTigers
WebTigers deleted the fix/datatable-statesave branch August 17, 2026 13:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant