tju-yxq opened a new pull request, #3294: URL: https://github.com/apache/rocketmq-dashboard/pull/3294
## What changed The Client Connections page now forwards the selected cluster and client type to the existing backend query parameters instead of loading every connection and filtering only in the browser. - send `clusterId` and `type` when a concrete filter is selected; - reset pagination when a filter changes; - calculate statistics, diagnostics, table rows, and exports from the filtered response; - keep all clusters from the registry in the cluster selector so filtering one response does not make other clusters disappear; - add regression coverage for combined filter requests and server-filtered statistics. ## Why On installations with many connections, the page could request and render the complete inventory even when an operator had selected a cluster or type. The displayed totals and exported data also depended on the client-side copy rather than the backend result. This makes the existing filters useful for large deployments and preserves the ability to switch back to another registered cluster after filtering. Closes #3291 ## Validation - `npm test -- ClientsPage.test.tsx --run` — 19 tests passed - `npm run lint -- --quiet` — 0 errors; 10 existing warnings remain elsewhere in the tree - `npm run build` — passed - `git diff --check` — passed The repository's CI status is not being described here; the validation above is from the local branch. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
