Symptom
The Schema Templates list paginates with PrimeNG's default p-table pager — just the page arrows. There is no rows-per-page selector, so the page size cannot be changed. Every other grid in the app shows the shared paginator with a 10 / 25 / 50 / 100 / 500 selector, so this grid is both inconsistent and less usable.
Where
frontend/src/app/views/schema-templates/schema-templates.component.html:88-89 enables the table's own paginator:
<p-table
[value]="templates"
[paginator]="true"
[rows]="pageSize"
...
The convention elsewhere is the shared <app-paginator> (frontend/src/app/modules/common/paginator/), as used by the Schemas grid.
Note
SchemaTemplatesComponent.onPage currently reads PrimeNG's {first, rows} payload:
public onPage(event: any): void {
this.pageIndex = Math.floor((event.first || 0) / (event.rows || this.pageSize));
this.pageSize = event.rows || this.pageSize;
this.loadTemplates();
}
app-paginator emits {pageIndex, pageSize} instead, so the handler has to change with the template. The default pageSize = 20 is also not one of the paginator's options, so it would be appended to the selector's list.
Symptom
The Schema Templates list paginates with PrimeNG's default
p-tablepager — just the page arrows. There is no rows-per-page selector, so the page size cannot be changed. Every other grid in the app shows the shared paginator with a 10 / 25 / 50 / 100 / 500 selector, so this grid is both inconsistent and less usable.Where
frontend/src/app/views/schema-templates/schema-templates.component.html:88-89enables the table's own paginator:The convention elsewhere is the shared
<app-paginator>(frontend/src/app/modules/common/paginator/), as used by the Schemas grid.Note
SchemaTemplatesComponent.onPagecurrently reads PrimeNG's{first, rows}payload:app-paginatoremits{pageIndex, pageSize}instead, so the handler has to change with the template. The defaultpageSize = 20is also not one of the paginator's options, so it would be appended to the selector's list.