Frun1na opened a new issue, #4805: URL: https://github.com/apache/rocketmq-dashboard/issues/4805
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) and found no similar issue. ### What Happened On the topic detail modal, the 消费模式 (message model) column of the consumer-group sub-table shows the raw API enum values (`CLUSTERING` / `BROADCASTING`, plus the vendor-native variants the Aliyun and Tencent providers pass through), and every row falls back to the blue tag — a broadcasting consumer never gets the orange highlight the column was written to show. The column matches `messageModel` against the display string the API returned before #3349: ```tsx render: (m: string) => <Tag color={m === '广播消费' ? 'orange' : 'blue'}>{m}</Tag>, ``` The Apache provider sends `conn.getMessageModel().name()` — `CLUSTERING` / `BROADCASTING` — so the comparison never matches any more. The i18n keys `topic.broadcast` / `topic.clustering` exist but are referenced nowhere, and `web/src/mock/topics.ts` still feeds the old display strings, which kept the dead comparison looking alive in the dev mock path. ### Expected Behavior The column should render the localized labels — `集群消费` (blue) and `广播消费` (orange) — for the enum values the API actually returns, with a raw-value fallback for anything unknown. ### Steps to Reproduce 1. Open an instance's Topic page and open a topic's 详情 modal with consumer groups attached. 2. Look at the 消费模式 column: values render as the raw `CLUSTERING` / `BROADCASTING` enums, all blue, including rows whose group is a broadcasting consumer. -- 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]
