Skip to content

Config store list: capped at 200 with no pagination, search, or sort #80

Open

Description

@ngAlexander9

Problem

src/components/ConfigStoreModal.tsx requests listConfigs({ pageSize: 200 }) in refresh() and discards both continuationToken and totalCount from the response. ListConfigsOptions.search exists in src/api/magpie.ts but no search input is wired into the modal.

Compounding this, the backend orders by a random UUID rather than by date (see slaclab/canopy — magpie config list ordering).

User-visible effect

  • Saved configs appear in arbitrary order, so a config you just saved lands at an unpredictable row.
  • Past 200 configs, entries become invisible with no indication that results were truncated — the list simply looks complete.

With a shared trace app namespace across users, 200 is not a comfortable ceiling.

Suggested fix

Frontend-only mitigations, independent of the backend change:

  • Sort by createdDate descending client-side so the list is predictable now.
  • Surface totalCount (e.g. "showing 200 of 340") so truncation is visible.
  • Wire up the existing search option.

Proper server-side ordering and paging requires the canopy-side fix; this issue tracks the frontend half.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions