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

   ## Problem
   
   The ACL risk diagnostics utility (`utils/aclRiskDiagnostics.ts`) returns 
**Chinese display text directly** — the status label (`ACL 配置健康` / `ACL 配置需要关注` 
/ `ACL 配置存在高风险`), all 15 issue variants' titles, descriptions, and per-issue 
recommendations (13 issue codes; the default-permission codes each have 
critical and warning variants). The ACL page renders these verbatim in the risk 
panel (status banner, issue table, recommendations list), so an operator who 
switches the console to English still gets an entirely Chinese risk diagnosis.
   
   This is the same gap fixed for the consumer group health diagnostics (#5564) 
and the topic route diagnostics (#5566): the codebase's established contract is 
that diagnostics utilities return translation keys and the page resolves them 
through `t()`.
   
   ## Expected behavior
   
   `analyzeAclRisk` follows the key-returning contract:
   
   - `statusText` → `statusKey` (`aclRisk.statusHealthy` / `statusWarning` / 
`statusCritical`)
   - each issue carries `titleKey` / `descriptionKey` / `recommendationKey` 
instead of `title` / `description` / `recommendation` (all texts are static; 
`evidence` stays raw data)
   - `recommendations` → `recommendationKeys` (the dedup-by-key builder and the 
6-item cap are unchanged)
   - the ACL page's risk panel resolves all of them through `t()`
   - the zh text is byte-identical to what the utility returned before, so 
Chinese-locale users see no change
   
   ## Notes
   
   - 47 new `aclRisk.*` entries in `translations.ts` (3 status + 15 
title/description pairs + 14 recommendations + 1 default recommendation).
   - The sibling `clientConnectionDiagnostics.ts` has the same gap and is 
tracked as the next member of the family.
   


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