Angular Datentabelle & Listen | ng-hub-ui-paginable

Angular Datentabelle und paginierte Liste mit serverseitiger Paginierung, Sortierung, Filterung, Auswahl, Templates und CSS-Variablen.

API-Referenz

Hier ist der vollständige Vertrag für paginable: alles, was du binden, abhören, projizieren und gestalten kannst, an einem Ort gesammelt. Verdrahte, was du brauchst, und gestalte, was du willst — es ist standalone und Signals-freundlich.

Inputs

Stelle paginable mit 31 Inputs ein. Binde sie wie jeden Angular-@Input.

NameTypStandardBeschreibung
dataErforderlichT[] | PaginationState<T> | nullTable data, bound with the `data` alias. Pass a plain array to let the table paginate/filter/sort in memory (client mode, when `paginate` is true and `totalItems` is unset); pass a `PaginationState` for server mode (the table renders it as-is and reads `page`/`perPage`/`totalItems` from it).
headersErforderlich(PaginableTableHeader | string)[]Column definitions. A string is shorthand for `{ property, title }`; a `PaginableTableHeader` enables sorting, per-column filters, buttons, sticky/visibility, alignment and templates. Two-way bindable (`model`).
pagenumber | nullCurrent 1-based page. Two-way bindable (`model`) — emits `pageChange`. Defaults to `null`.
perPagenumber | nullItems per page. Two-way bindable (`model`) — emits `perPageChange`. Defaults to `10`.
perPageOptionsnumber[]Selectable page sizes shown in the per-page selector. Defaults to `[10, 20, 50, 100]`.
totalItemsnumber | nullTotal number of items across all pages (server mode). Setting it keeps the table in server mode even for a plain array. Two-way bindable (`model`) — emits `totalItemsChange`.
paginatebooleanEnables pagination. When `true` (default) with a plain array and no `totalItems`, the table searches, filters, sorts and slices in memory (client mode). Set `false` to render the whole array without pagination.
ordinationPaginableTableOrdinationActive sort (`{ property, direction }`). Two-way bindable (`model`) — emits `ordinationChange` when a sortable header is clicked.
searchablebooleanShows the global search box. Defaults to `true`.
searchTermstringGlobal search term. Two-way bindable (`model`) — emits `searchTermChange` (debounced by `debounce`).
filtersRecord<string, unknown> | nullPer-column filter values keyed by `filter.key` or `property`. Two-way bindable (`model`) — emits `filtersChange`.
selectableSelectionTypes | boolean | nullEnables row selection (`true`/`single` or `multiple`). The selected value is read/written through `ControlValueAccessor` (`[(ngModel)]` or a `formControl`).
multiplebooleanForces multiple selection regardless of `selectable`. Defaults to `false`.
bindValuestringProperty of each row used as the selection value instead of the whole object.
clickFn(event: TableRowEvent<T>) => void | Promise<void>Callback invoked when a row is clicked, receiving the row data plus the originating event.
rowClassstring | ((item: T) => string)CSS class applied to every row, either a fixed string or a function of the row data.
responsiveTableBreakpoint | nullBreakpoint at which the table switches to its responsive (stacked) layout.
paginationPosition'bottom' | 'top' | 'both'Where the pagination controls are rendered (`bottom`, `top` or `both`). Defaults to `bottom`.
paginationInfobooleanShows the "Showing X of Y" info line. Defaults to `true`.
stickyActionsbooleanKeeps the row action column stuck to the viewport while scrolling. Defaults to `false`.
stickyHeaderbooleanPins the header (`position: sticky; top: 0`) while the body scrolls, inside any consumer `max-height`/`overflow:auto` container — decoupled from `options.scrollable`. Overridable via `--hub-table-head-position`. Defaults to `false`.
flushFieldsbooleanfalseDraws the form controls inside the cells as a spreadsheet does: no border, no surface of their own. A field is boxed so it can be told apart from the page around it, and a table cell already does that job — so the box gets drawn twice and an editable table reads as a form that fell into a table. Static prepend/append content loses its chip and reads as the plain text or icon it is; a projected button stops being welded to its neighbour, getting its corners back, a gap and its own border colour, because two actions in a cell are two things to press rather than one strip. The control regains its shared corners too. It is a token assignment on the cells rather than an input on each field, which is both why it reaches your own cellTpt content and why it needs ng-hub-ui-forms 22.21.0 for the seam tokens.
flushbooleanDraws the collection as a list rather than as a stack of cards: no border, radius or surface per row, a rule between them instead. On `hub-table` it drops the outer border, the radius, the head rule and the cell padding while keeping the row divider, because a table with no line between rows stops being readable across its columns. Right for a list of choices inside a dialog or a panel, where the surface has already drawn the frame. An input rather than something CSS can reach: the token defaults sit on the host, so a consumer class on the same element ties on specificity and loses on source order. Defaults to `false`.
batchActions(PaginableTableDropdown | PaginableActionButton)[]Actions shown in the toolbar that operate on the currently selected rows.
debouncenumberDebounce in milliseconds applied to search and filter changes. Defaults to `0`.
optionsPaginableTableOptionsVisual/behavioural options: `striped`, `hoverableRows`, `variant`, `cursor`, `scrollable`, `rtl`…
loadingbooleanRenders the loading state. Two-way bindable (`model`) — emits `loadingChange`.
errorunknown | nullWhen truthy, renders the error state. Two-way bindable (`model`) — emits `errorChange`.
loadingComponentPaginableStateDefault | nullPer-instance default component for the loading state.
errorComponentPaginableStateDefault | nullPer-instance default component for the error state.
noResultsComponentPaginableStateDefault | nullPer-instance default component for the no-results state.

Outputs

Reagiere darauf, was paginable tut — 9 Events, an die du deine Logik anknüpfen kannst.

NameTypBeschreibung
pageChangenumber | nullEmitted by the two-way `page` model when the current page changes.
perPageChangenumber | nullEmitted by the two-way `perPage` model when the page size changes.
totalItemsChangenumber | nullEmitted by the two-way `totalItems` model (e.g. when a `PaginationState` is bound).
ordinationChangePaginableTableOrdinationEmitted by the two-way `ordination` model when sorting changes — use it to drive server-side sorting.
filtersChangeRecord<string, unknown> | nullEmitted by the two-way `filters` model when a column filter changes — use it to drive server-side filtering.
searchTermChangestringEmitted by the two-way `searchTerm` model when the global search changes (debounced by `debounce`).
loadingChangebooleanEmitted by the two-way `loading` model.
errorChangeunknown | nullEmitted by the two-way `error` model.
headersChange(PaginableTableHeader | string)[]Emitted by the two-way `headers` model when the column configuration changes.

Templates

Mach es zu deinem — 7 Template-Slots lassen dich eigenes Markup projizieren.

NameBeschreibungBeispiel
*paginableTableHeaderBenutzerdefiniertes Header-Template zum Definieren benutzerdefinierter Spaltenüberschriften<ng-template *paginableTableHeader="let column">{{ column.title }}</ng-template>
*paginableTableCellBenutzerdefiniertes Zellen-Template zum Anpassen des Renderns von Zelleninhalten<ng-template *paginableTableCell="let value; let row">{{ value }}</ng-template>
*paginableTableRowBenutzerdefiniertes Zeilen-Template zum Definieren der gesamten Zeilenstruktur<ng-template *paginableTableRow="let row"><tr>...</tr></ng-template>
*paginableTableFilterBenutzerdefiniertes Filter-Template zum Hinzufügen von Filter-UI-Elementen<ng-template *paginableTableFilter="let column"><input type="text"></ng-template>
*paginableTableLoadingLadezustands-Template für benutzerdefinierte Ladeindikatoren<ng-template *paginableTableLoading><div class="spinner"></div></ng-template>
*paginableNoResultsLeerzustands-Template, das angezeigt wird, wenn keine Daten verfügbar sind<ng-template *paginableNoResults><p>No data found</p></ng-template>
*paginableTableErrorFehlerzustands-Template zur Behandlung von Fehlerbedingungen<ng-template *paginableTableError="let error"><p>Error: {{ error }}</p></ng-template>