Skip to content

perf(frontend): make transfer search and filtering deterministic at scale #281

Description

@arisu6804

Problem

Client filtering and request fan-out become slow and race-prone as transfer history grows.

Objective

Deliver a production-quality improvement to transfer search, filters, and result loading that creates measurable value for correctness, security, reliability, performance, or maintainability.

Implementation scope

  • Debounce and cancel obsolete queries; cap results; define stable filter and sort semantics; keep actor scope in every request.

Acceptance criteria

  • Stale responses cannot overwrite current filters; request volume is bounded; large histories remain responsive.

Required validation

  • Race, cancellation, scope, pagination, and performance tests.
  • Existing tests and CI remain passing.
  • Add regression coverage for the original failure mode.
  • Do not weaken, delete, or skip unrelated tests to obtain a green build.

PR quality bar

  • Keep the PR focused and explain design tradeoffs, compatibility impact, and test evidence.
  • Avoid typo-only, documentation-only, cosmetic-only, or unrelated refactor submissions.

Out of scope

  • Broad rewrites not required by the acceptance criteria.
  • Changes to unrelated services, contracts, or user flows.

Metadata

Metadata

Assignees

No one assigned

    Labels

    GRANTFOX OSSOpen-source issue tracked by GrantFoxMAYBE REWARDEDThis issue may carry a rewardThird CampaignThird Campaign contributionenhancementNew feature or requestpriority:mediumMedium implementation priority

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions