* 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 |
|---|---|---|
| .. | ||
| dialogs | Loading commit data... | |
| drawers | Loading commit data... | |
| data-table-bulk-actions.tsx | Loading commit data... | |
| data-table-row-actions.tsx | Loading commit data... | |
| deployment-access-guard.tsx | Loading commit data... | |
| deployments-columns.tsx | Loading commit data... | |
| deployments-table.tsx | Loading commit data... | |
| description-cell.tsx | Loading commit data... | |
| models-columns.tsx | Loading commit data... | |
| models-dialogs.tsx | Loading commit data... | |
| models-primary-buttons.tsx | Loading commit data... | |
| models-provider.tsx | Loading commit data... | |
| models-table.tsx | Loading commit data... | |
| prefill-group-shared.ts | Loading commit data... |