Add pagination to ISAC registries
This commit is contained in:
@@ -239,3 +239,20 @@ creating a new record keeps the editor open with a fresh blank definition for
|
||||
rapid consecutive entry. Failed validation leaves the current editor and
|
||||
entered values intact. Use a unique action result token so reactive handling
|
||||
runs exactly once and does not create update loops.
|
||||
|
||||
Tiered-definition registries should show their rendered tier effects when the
|
||||
text is operationally useful. Use compact wrapping description cells rather
|
||||
than replacing meaningful data with a generic “configured” label; retain an
|
||||
explicit textual missing state when a tier has no rendered description.
|
||||
|
||||
### Registry pagination
|
||||
|
||||
Every primary ISAC registry uses server-side pagination. The shared control
|
||||
appears immediately above and visually attached to its table. It shows the
|
||||
visible record range and total, previous/next navigation, a compact
|
||||
window of page numbers, and row-count presets of 10, 25, 50, and 100. Existing
|
||||
filter query parameters must survive page navigation, while changing page size
|
||||
returns to page one. Summary metrics remain global or filter-global and must
|
||||
never silently describe only the visible page. On narrow screens, retain
|
||||
previous, next, current page, and page-size controls before optional page
|
||||
numbers.
|
||||
|
||||
Reference in New Issue
Block a user