tju-yxq opened a new pull request, #3290: URL: https://github.com/apache/rocketmq-dashboard/pull/3290
## What happened The backend already returns message properties with every message record: ```java private Map<String, String> properties; private boolean propertiesTruncated; ``` The Apache provider bounds this payload to 64 properties and 1,024 characters per value, and sets `propertiesTruncated` when that display contract shortens the payload. The frontend never showed it: - the Message Explorer detail modal displayed basic metadata and the body only; - queue-browser message cards showed Message ID, Tag, Key, store time, size, born host, and body; - the frontend `MessageRecord` type did not include `propertiesTruncated`. Operators therefore could not inspect trace flags, retry context, routing metadata, or business user properties in the UI even though the backend delivered them. ## Change - Add `propertiesTruncated` to the frontend message contract. - Show a bounded **消息属性** section in the message detail modal. - Show a **Properties** card in queue-browser message cards. - When the server shortened the payload, show a warning explaining that properties were truncated. - Keep body display and existing metadata unchanged. - Update message fixtures and add a regression test for property rendering and truncation. ## Verification Focused frontend: ``` cd web npm test -- MessagePageAsyncState.test.tsx MessagePage.test.tsx QueueBrowser.test.tsx message.test.ts --run ``` Result: 5 files / 45 tests passed. Lint/build: ``` npm run lint -- --quiet npm run build ``` Lint reported 0 errors and 10 pre-existing warnings elsewhere. The production build passed. `git diff --check` passed before commit. This is a 92-line frontend-only change. It is the natural size for surfacing data that the backend already returns; no unrelated backend or padding changes were added. Closes #3282 -- 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]
