Aias00 opened a new issue, #682: URL: https://github.com/apache/rocketmq-dashboard/issues/682
### Problem The Studio Proxy page presents the Proxy node configuration modal as if it were showing real runtime configuration, but the data is synthesized in the browser. Current code in `web/src/pages/studio/Proxy.tsx` builds `nodeConfig` from hardcoded values inside `handleViewConfig`, including values such as `proxy.maxConnections`, `proxy.threadPoolSize`, `proxy.enableACL`, and `rocketmq.namesrv.addr`. The comment also states that the page uses simulated config data because no config endpoint is available. This is misleading for operators: a user can open the Proxy config modal and believe the displayed values came from the selected Proxy node, while they are only placeholders. ### Scope RocketMQ Studio Track 1 / ARCH-01 Proxy management view. ### Expected behavior - The Proxy config modal should not display fabricated configuration as real data. - If a real Proxy config API is unavailable, the UI should clearly degrade to an unavailable/unsupported state instead of rendering fake values. - The page should keep existing Proxy address add/remove behavior unchanged. ### Proposed fix Remove the hardcoded simulated config payload from the Proxy page. When config data is unavailable, show a clear empty/unsupported state in the modal or disable the action until a real backend contract exists. ### Validation Add a frontend regression test to assert that opening the Proxy config action does not render fake hardcoded config values when no backend config data is available. -- 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]
