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

   ## Summary
   
   The instance list page (instance/index.tsx) only localized its page heading; 
table headers, toolbars, toasts, delete confirmations and both add/edit forms 
were hard-coded zh.
   
   This PR localizes the whole page:
   - Header, subtitle (parameterized with the visible count), search box and 
the type filter reuse existing `instance.*` keys (`instance.searchPlaceholder`, 
`instance.allTypes`, ...) plus new mode labels (`instance.typeCloud`, 
`instance.proxyLocalMode`, `instance.proxyClusterMode`).
   - Table headers and cells (region/开源版, instance ID, remark, vendor, type 
tag, topic/group unavailable, created/updated, actions) route through keys; 
type tags resolve via a label-key map.
   - All result toasts are parameterized: create/update/delete/batch-delete, 
the one-click import summary chain 
(`importComplete`/`importIncomplete`/`importNoneNeeded` plus failure 
suffix/omitted/details), and both delete-confirmation dialogs (single and 
batch, cloud vs open-source warning texts).
   - The add-instance modal (cloud credential / region / cloud instance 
selectors with hint + empty-state links, instance ID rules, remark) and the 
edit modal (access type, endpoint with long-form help tooltip and per-mode 
hints/placeholders, credential reference) are fully localized; the endpoint 
tooltip is shared between the two forms.
   - Lists joined in UI text use a language-aware separator (、 vs ", ", ; vs "; 
").
   - Reuses ~24 existing `instance.*` keys and adds ~73 new ones; no behavior 
change (zh byte-identical).
   
   ## Why
   
   The instance page is the entry point for every instance-scoped surface; its 
management flows (add / import / edit / delete) must read in the active 
language.
   
   ## Testing
   
   - `tsc --noEmit` passes
   - `eslint` clean on the changed files
   - `vitest run InstancePage` - 22/22 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