The Domains page lists every served domain and every history row without paging #36

New Issue

2026-09-21T07:18:11Z

cgalo5758 commented

2026-09-21 07:18:11 +00:00

What happens

The operator's Domains page has three tables. The claims table is paged and searchable. The placements table and the history table render every row they have, with no search, no paging and no total. Served names outnumber claims on any deployment that places more than one name per claim, so the placements table is the longest one on the page and the only one without controls.

What should happen

Every list on an operator page is paged and searchable, with its true total in the section header. That is the rule the rest of the console follows, and the lint that enforces it checks one table per template, so a second table beside a governed one never trips it.

Where

internal/server/operator_domains.go, the placements and history loaders; internal/lint/anatomy.go, the table-without-list-controls rule.

Why it matters

An operator with a few hundred served names scrolls a wall of rows to find one, and the page reads as if nothing is paged when the claims table fits on one screen.

Done when both tables page with their own parameter prefix, placements search by served name and organization, each section header shows its total, and the lint rule catches a second table on the same template.

Migrated from status/issues.md at b7a0e15

## What happens The operator's Domains page has three tables. The claims table is paged and searchable. The placements table and the history table render every row they have, with no search, no paging and no total. Served names outnumber claims on any deployment that places more than one name per claim, so the placements table is the longest one on the page and the only one without controls. ## What should happen Every list on an operator page is paged and searchable, with its true total in the section header. That is the rule the rest of the console follows, and the lint that enforces it checks one table per template, so a second table beside a governed one never trips it. ## Where [`internal/server/operator_domains.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/server/operator_domains.go), the placements and history loaders; [`internal/lint/anatomy.go`](https://git.coopcloud.tech/wiki-cafe/member-console/src/commit/b7a0e15/internal/lint/anatomy.go), the table-without-list-controls rule. ## Why it matters An operator with a few hundred served names scrolls a wall of rows to find one, and the page reads as if nothing is paged when the claims table fits on one screen. Done when both tables page with their own parameter prefix, placements search by served name and organization, each section header shows its total, and the lint rule catches a second table on the same template. Migrated from status/issues.md at b7a0e15

cgalo5758 added this to the Public launch milestone 2026-09-21 07:18:11 +00:00

cgalo5758 added the

kind

bug

area/domains area/operator-ui

priority

medium

labels 2026-09-21 07:18:11 +00:00

Sign in to join this conversation.