tju-yxq opened a new issue, #5571:
URL: https://github.com/apache/rocketmq-dashboard/issues/5571
## Problem
The send pre-check family returns **Chinese display text directly**:
1. **`utils/messagePayloadPreview.ts`** — the pre-send check in the topic
page's send modal. All 14 issue types carry hardcoded `title` / `description`
strings, several with interpolated values (duplicate property names, reserved
names, empty-value names, body/property byte counts, count limits). The send
modal renders them verbatim in the pre-check panel, and the blocking toast
joins the titles — all Chinese regardless of the display language.
2. **`utils/messageProperties.ts`** — the batch-paste property parser
returns `errors: string[]` with three interpolated Chinese messages (`“…”应使用
key=value 格式` etc.), which flow into the pre-check's `INVALID_PROPERTY_FORMAT`
issue descriptions.
This is the same gap fixed for the consumer (#5564), route (#5566), ACL
(#5568), and client-connection (#5570) diagnostics: the established contract is
that analysis utilities return translation keys and the page resolves them
through `t()`.
## Expected Behavior
- `MessagePayloadIssue` carries `titleKey` / `descriptionKey` plus optional
`params` (value, names, bytes, max, count) instead of `title` / `description`;
`names` stays raw data.
- `parseMessageProperties` returns structured errors (`{ key, params }`)
instead of interpolated strings; the pre-check maps them straight into the
issue's `descriptionKey` / `params`.
- The send modal's pre-check panel and blocking toast resolve everything
through `t(key, params)`.
- The zh text is byte-identical to what was returned before, so
Chinese-locale users see no change.
## Notes
- ~35 new keys: a `sendCheck.*` section (14 title/description pairs) and a
`propErr.*` section (3 parser errors), plus `topic.precheckBlockedToast` /
`topic.listSeparator` for the toast.
- The sibling `resourceCsvImport.ts` (topic/consumer CSV import validation)
has the same gap and is tracked separately.
--
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]
