yyqdbngt opened a new pull request, #3199:
URL: https://github.com/apache/rocketmq-dashboard/pull/3199

   ## Summary
   
   The topic page is being localized in slices (send-message, list/toolbar, 
create, import/sync done previously); this PR covers the route diagnostics and 
the detail information in the topic detail modal.
   
   Localized in instance/topic.tsx:
   - Module maps now resolve through the translator: `PERM_LABEL` (RW/RO/WO) 
maps to existing `topic.permRW/RO/WO` keys, and the route status meta carries 
label keys (健康 / 关注 / 异常).
   - Route table columns and cells: 地址拓扑, the 地址未知 empty state, 队列分布 with 
per-row 写队列 n / 读队列 n labels, 权限 with 读/写 access tags, and the 诊断 column; the 
no-issues empty state (无).
   - Route diagnostics panel: 诊断项 title, issue severity tags (异常 / 关注), 建议处理 
banner title, 路由信息 section header, the diagnostics banner (路由诊断:{status}), 
healthy vs issue summary sentences, and the 在 Broker 上重建 action.
   - Route metric cards: Broker 数, 可写 Broker, 可读 Broker, Replica 数 and their 
count extras ({n} 个地址 / 写队列 / 读队列), plus the queue-skew vs balanced fallback.
   - Detail descriptions: Topic 名称 / 类型 / 集群 / 写队列数 / 读队列数 / 权限 / 今日消息量 / TPS / 
消费者组数 / 创建时间 (all reusing existing `topic.*` keys) and the perm tag through the 
keyed map.
   - The consumer table columns inside this modal are intentionally untouched 
(covered by the pending consumer-panel localization).
   - 25 new `topic.*` keys; zh byte-identical.
   
   ## Why
   
   The route diagnostics are the richest health surface of the topic detail 
view; their labels and guidance must follow the active language.
   
   ## Testing
   
   - `tsc --noEmit` passes
   - `eslint` clean on the changed files
   - `vitest run TopicPage` - 21/21 tests pass


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