[hisco]

The resource table drops its sort on every kind switch. Sort Pods by Restarts, open Deployments, come back, and Pods is in its built-in order again. Reproduce on main: open Resources, click any column header, click another kind in the sidebar, click back.

The table already remembers which columns show, their widths and any custom columns, per kind, in the browser. Sort was the one thing it forgot.

Continues #529 by @7adityaraj. The first commit is theirs and adds one global sort preference. The second reworks it into per-table memory, so the Settings section and server field it added are removed again there.

What this does

Sort gets its own per-kind record, stored beside the column settings. A header click is remembered for that table and restored when the user comes back to it, across kind switches and reloads. Cycling a sort off clears it. Nothing carries between tables: sorting Nodes by Status leaves Pods alone.

There is no setting to find and nothing new in Settings. It behaves the way column visibility already does.

Where to look hardest

effectiveSortColumn in ResourcesView. State holds the sort that was chosen or restored. Whether it is in force is decided at render time: it applies only while this table can currently sort by that column. A saved column can name one the table no longer renders (a custom column since removed, a CRD whose printer columns changed) or one that has not loaded yet. Applying it blind would order rows by an absent value with no header arrow to undo it from. Deciding at render time also means a column that arrives later takes effect on its own, with no reset and no second pass.

Why sort is not inside the column record. The existence of a column record is read elsewhere as "the user chose columns": GPU auto-show stands down behind it, and the stale-defaults migration skips it. A sort is not that choice, so it lives in a sibling radar-sort-<kind> key with the same per-kind scoping. It is written at the click in handleSort, the only place it changes, rather than through the column-settings save effect, so a kind switch cannot write one kind's sort under another kind's key.

The shortcut guard in handleSort. The N/A/S shortcuts fire on every kind, including ones with no such column. Without the guard they would save a sort the table cannot show.

Deliberately not in scope

• No sync across browsers or devices. Same as the column settings this sits beside.
• No global "sort everything by X". One preference for every table meant a click on one table changed all of them.
• Radar Hub gets this through the shared component with no change on its side, as it does for column visibility.

What it looks like

1. Pods, nothing sorted, built-in order.

2. Pods sorted by Restarts.

3. Deployments, unaffected by the Pods sort.

4. Deployments sorted by Age, newest first.

5. Back on Pods: still Restarts.

6. Back on Deployments: still Age.

7. After a full reload: still sorted.

8. Restarts cycled off on Pods: forgotten.

9. A user-defined label column, remembered like any other.

10. That column removed: no arrow and no hidden ordering.

Tests

• packages/k8s-ui: the saved-sort sanitizer at the localStorage boundary.
• Driven in a browser against cmd/testserver: two kinds keep separate sorts, a sort alone writes no column record, both survive a reload, cycling off clears the record, a shortcut on a kind without the column saves nothing, a user-defined column is remembered, a removed column produces no invisible sort and an order identical to no sort at all, a corrupt record is ignored.

Closes #529.

Co-authored-by: 7adityaraj 17121540+7adityaraj@users.noreply.github.com

---

Note

Low Risk
Client-only localStorage and render-time guards; no auth or API changes, with bounded impact if saved sort data is corrupt.

Overview
The resource table remembers column sort per kind in localStorage (separate radar-sort-* keys from column visibility), so switching kinds or reloading no longer clears a header sort.

sanitizeSavedSort validates stored sort blobs; loadSavedSort / saveSavedSort read and write on kind load, header clicks, and column reset. Sort state is not cleared on kind change anymore (filters still are). effectiveSortColumn only applies a restored sort while that column is currently sortable; canSortBy blocks shortcuts and saves for non-sortable columns. Sorting and header arrows use the effective column so removed or not-yet-loaded columns cannot impose invisible ordering.

Adds unit tests for sanitizeSavedSort.

^{Reviewed by Cursor Bugbot for commit de75f7c. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 2bba2c3. Configure here.}