tju-yxq opened a new issue, #2587:
URL: https://github.com/apache/rocketmq-dashboard/issues/2587

   ## Problem
   
   The repository currently contains two consumer group management UIs:
   
   1. the active instance-scoped page at `/instance/consumer`;
   2. a legacy global page at `/studio/group-management`.
   
   The legacy page is unreachable from the current navigation: no menu, button, 
link, or documented path points to `/studio/group-management`. It exists only 
as a retained route plus a lazy-loaded page module.
   
   It also duplicates behavior that has since diverged:
   
   - it calls `listConsumerGroups()` without an instance filter;
   - it performs search and pagination entirely in memory;
   - it maintains its own diagnostics modal, polling, status, formatting, and 
translations;
   - the active page is server-paginated and instance-scoped, and already 
supports the real lifecycle and diagnostics flows.
   
   Keeping the unreachable page leaves about 576 lines of stale production 
code, 399 lines of tests, and a separate `groupMgmt.*` translation namespace 
that must be maintained despite never being exposed through navigation.
   
   ## Expected behavior
   
   - Remove the unreachable legacy page component and its tests.
   - Remove the lazy import and dead route component.
   - Keep a redirect at `/studio/group-management` so any old bookmark lands on 
the active `/instance/consumer` page instead of a blank screen.
   - Remove the now-unused `groupMgmt.*` translations.
   - Do not alter the active instance-scoped consumer page.
   
   ## Verification scope
   
   - Build should pass.
   - Lint should have no new errors.
   - Search should show no remaining `GroupManagement` implementation or 
`groupMgmt.*` translation usage.
   - Existing full-suite failures should be shown to be pre-existing on the 
untouched upstream baseline when necessary.
   


-- 
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]

Reply via email to