RockteMQ-AI commented on issue #2002: URL: https://github.com/apache/rocketmq-dashboard/issues/2002#issuecomment-5265322548
**Issue Evaluation** Category: | Status: **Evaluated** The API spec drift is well-documented and the affected endpoints are clearly enumerated. Cross-referencing against the controllers and DTOs you listed confirms the mismatches: - **Message/Trace/DLQ endpoints**: missing or incorrect scope parameters - **DLQ resend**: wrong field types (ISO strings vs epoch-millis), incorrect null response documentation - **Client connections**: missing - **NameServer CRUD**: missing , wrong field names ( vs ), missing This is a straightforward documentation fix — no code behavior changes needed. The suggested scope (Message, DLQ, Client, NameServer sections only) is appropriate. **Feasibility:** feasible **Scope:** only **Compatibility:** no breaking changes A PR to align the spec with the current controller implementations should resolve this. --- *Automated evaluation by RockteMQ-AI* -- 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]
