btlqql opened a new pull request, #2571: URL: https://github.com/apache/rocketmq-dashboard/pull/2571
## What is the purpose of the change The backend already reports `bodyEncoding`, `bodyTruncated` and `propertiesTruncated` on every message record, but the frontend type dropped all three fields. Base64-encoded binary bodies were therefore rendered and downloaded as if they were complete plain text: the detail view pretty-printed the encoded string as JSON, and the download button always wrote a `.json` file. ## Brief changelog - complete the `MessageRecord` type with the three metadata fields - the detail view now shows truncation warnings for clipped bodies and property maps, and marks Base64 bodies with a tag - downloads pick the content and extension from the encoding: Base64 bodies are saved verbatim as `.txt`, UTF-8 bodies keep the JSON pretty-printing behavior ## How was this patch verified - new `MessageBodyEncoding` page tests (3/3 green): detail warnings for truncated body/properties and the Base64 marker, no warnings for plain UTF-8 bodies, and download content/extension per encoding - `web/src/api/message.test.ts` 7/7 green; `tsc -b` and `eslint` clean - remaining MessagePage test failures are pre-existing on the base branch (recent-query button removed in a later refactor) Fixes #2501 -- 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]
