* fix: add server-side sorting to user list, prevent client-side sort on paged data The user management table applied client-side sorting to the current page slice while pagination was handled server-side, causing ID-asc views to show pages out of order (e.g. 23-42, 3-22, 1-2). Backend: add sort_by/sort_order query params to GetAllUsers and SearchUsers with a column whitelist for safe ORDER BY generation. Frontend: pass sorting state to the API and reset to page 1 on sort change. Generic useDataTable hook now disables client-side sorted row model and sort UI for tables with manual pagination but no server-side sort handler. * fix: add id tie-breaker to non-unique sort columns, remove side effect from state updater Append secondary ORDER BY id DESC when sorting by non-unique columns (quota, created_at, etc.) to prevent row duplication/skipping across OFFSET pages. Move onPaginationChange out of setSorting updater to avoid side effects inside a pure function (React Strict Mode double-invocation safety).
| Name |
Last commit
|
Last Update |
|---|---|---|
| .. | ||
| assets | Loading commit data... | |
| components | Loading commit data... | |
| config | Loading commit data... | |
| context | Loading commit data... | |
| features | Loading commit data... | |
| hooks | Loading commit data... | |
| i18n | Loading commit data... | |
| lib | Loading commit data... | |
| routes | Loading commit data... | |
| stores | Loading commit data... | |
| styles | Loading commit data... | |
| env.d.ts | Loading commit data... | |
| main.tsx | Loading commit data... | |
| routeTree.gen.ts | Loading commit data... | |
| tanstack-table.d.ts | Loading commit data... |