RockteMQ-AI commented on issue #1297: URL: https://github.com/apache/rocketmq-dashboard/issues/1297#issuecomment-5231448249
**Issue Evaluation** Category: `enhancement` | Status: **Evaluated** **Feasibility:** feasible **Scope:** `LiteTopicController`, `LiteTopicService`, `web/src/api/liteTopic.ts`, `web/src/pages/studio/LiteTopic.tsx` **Compatibility:** No breaking changes — the current service returns 501, so adding instance-scoped parameters is additive. The design gap is real. The current `LiteTopicService` intentionally returns 501 because no live provider/Admin contract exists, and the API endpoints are global (no instance context). Defining an instance-scoped provider contract before wiring the UI is the correct approach. The proposed contract (capability, list, quota, session, extendTtl — all scoped by instanceId) is well-structured. The provider should declare supported instance types so the UI can gate availability accordingly. **Recommendation:** Proceed with the proposed contract definition. Consider also defining error responses for unsupported instance types. --- *Automated evaluation by github-manager-bot* -- 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]
