tju-yxq opened a new issue, #5565:
URL: https://github.com/apache/rocketmq-dashboard/issues/5565
## Problem
The topic route diagnostics utility (`utils/topicRouteDiagnostics.ts`)
returns **Chinese display text directly** — the overall status label (`路由健康` /
`需要关注` / `不可用`), all 14 issue types' titles and descriptions, and eight
recommendation sentences. The topic page's route section renders these verbatim
(the diagnostics alert, the per-broker issue list, the recommendations banner,
and the issue tags in the route table), so an operator who switches the console
to English still gets an entirely Chinese route diagnosis.
This is the same gap fixed for the consumer group health diagnostics in
#5564: the codebase's established contract (from `messageTraceDiagnostics`) is
that diagnostics utilities return translation keys and the page resolves them
through `t()`. `topicRouteDiagnostics` is the second member of the family of
six key-less diagnostics utils.
## Expected behavior
`analyzeTopicRoutes` follows the key-returning contract:
- `statusText` → `statusKey` (`routeDiag.statusHealthy` / `statusWarning` /
`statusCritical`)
- each issue carries `titleKey` / `descriptionKey` instead of `title` /
`description` (all texts are static — no interpolation params are needed)
- `recommendations` → `recommendationKeys`
- the topic page's route section resolves all of them through `t()`; the
status alert becomes `路由诊断：{status}` / `Route diagnostics: {status}` with the
status itself translated
- the zh text is byte-identical to what the utility returned before, so
Chinese-locale users see no change
## Notes
- 39 new `routeDiag.*` entries plus one `topic.routeDiagnostics` page key.
- The page change overlaps #5533 on a single line (the status alert);
whichever lands second needs a trivial rebase.
--
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]
