Frun1na opened a new issue, #4972:
URL: https://github.com/apache/rocketmq-dashboard/issues/4972

   ### Problem
   
   Two failure/status surfaces stay Chinese after the console language is 
switched to English.
   
   **1. Global API error handling (`web/src/api/client.ts`)**
   
   The axios response interceptor produced both of its generic messages as 
Chinese literals:
   
   - a failed business envelope with no `message` was surfaced as `请求失败`;
   - a CORS rejection (Spring answers a non-allow-listed origin with `403` and 
a plain-text body) was surfaced as `请求被服务端 CORS 策略拒绝(Invalid CORS request):…`.
   
   Those two paths are the app's most generic errors — every module that does 
not carry its own message, and the failure mode of a misconfigured deployment — 
so an English operator gets a Chinese toast with no way to read it.
   
   **2. Home page build stamp (`web/src/pages/home/index.tsx`)**
   
   The footer rendered `当前版本 <time> build(<commit>)` as a literal. The rest of 
that page (banner, greetings, tagline, docs / community / brand links, composer 
placeholder) is translated.
   
   ### Steps to reproduce
   
   1. Switch the console language to English.
   2. On the home page, read the footer: it still says `当前版本 …`.
   3. Trigger a request whose business envelope has no `message` (or load the 
console from an origin missing from `STUDIO_CORS_ALLOWED_ORIGINS`): the toast 
is Chinese.
   
   ### Expected
   
   Both follow the selected language, like the rest of the console.
   
   ### Fix
   
   PR: #4971 — adds `common.requestFailed`, `common.corsRejected` and 
`home.version` and routes both surfaces through them. The Chinese values are 
copied verbatim, so the Chinese UI does not change; only the English UI gains 
text.
   


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