RockteMQ-AI commented on PR #4269: URL: https://github.com/apache/rocketmq-dashboard/pull/4269#issuecomment-5658822062
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** Feasible **Scope:** `DeadLetterRecordVO`, `RocketMQDlqProvider.toDlqRecordVO`, `DeadLetterMessageDrawer.jsx` **Compatibility:** No breaking changes — additive field with graceful fallback. Well-structured request. The DLQ detail drawer is the most critical surface for `reconsumeTimes` — this is where operators triage permanently-failed messages and need to see how many redelivery attempts were made before the message landed in `%DLQ%`. The implementation mirrors the same pattern as the message detail panel (#4271): add the field to the VO, populate from `MessageExt` in the provider mapping, render in the frontend drawer. The `DeadLetterMessageVO` already carries related metadata (storeTime/bornTime), so `reconsumeTimes` fits naturally alongside. The note about cloud-provider VO builders defaulting to `0` is consistent with existing fields (e.g., `queueId`) and is acceptable. Clean, low-risk enhancement. Pairs well with #4271 as a coordinated metadata completeness improvement. --- *Automated evaluation by github-manager* -- 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]
