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

   ## Summary
   
   The consumer group page is still being localized in slices; this PR covers 
the offset-reset flow (the riskiest action on the page), which was entirely 
hard-coded zh.
   
   Localized in instance/consumer.tsx:
   - The preview table columns (当前位点 / 目标位点 / 变化 / 当前堆积 / 重置后堆积 / 风险 / 说明) and 
the per-queue impact message builder (`resetPreviewQueueMessage` now takes the 
translator and builds lang-aware text: replay / skip / unchanged / min-retained 
/ latest-offset hints joined with the active language separator).
   - The risk labels (失败 / 需确认 / 正常) and all reset handlers feedback: 
missing-Topic warning, preview-complete toast, preview-not-confirmed warning, 
preview failure reason and the success toast (`{name} 在 {topic} 的消费位点已重置到 
{time}`).
   - The reset modal: title, confirm/cancel, the impact alert (title + long 
description), target group/topic fields, topic placeholder and not-found 
states, time picker label/placeholder, quick-select presets (1/3/6/12 小时前, 1/3 
天前), the preview notice, preview button, preview error, the summary 
descriptions (Queue 数 / 当前总堆积 / 重置后总堆积 / 位点净变化 / 回放 Queue / 跳过 Queue / 预览状态 
with 完整/有限/不完整 tags), the confirm-impacts alert and the empty-table text.
   - Reuses existing keys (`consumer.resetOffset`, `consumer.resetFailed`, 
`common.cancel`); 52 new `consumer.*` keys added; zh byte-identical, so visuals 
are unchanged.
   
   ## Why
   
   Offset reset changes consumption position; every warning and confirmation in 
this flow must be readable in the active language.
   
   ## Testing
   
   - `tsc --noEmit` passes
   - `eslint` clean on the changed files
   - `vitest run ConsumerPage` - 29/29 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