Copilot commented on code in PR #801:
URL:
https://github.com/apache/rocketmq-dashboard/pull/801#discussion_r3701811143
##########
web/src/pages/studio/LiteTopic.tsx:
##########
@@ -204,7 +204,12 @@ const LiteTopicPage: React.FC = () => {
}
} catch {
if (!bootstrapIsActive()) return;
- // Assume supported when capability detection is unavailable.
+ ++displayCounter.current;
+ setCapabilitySupported(false);
+ setTopicList([]);
+ setQuota(null);
+ setLoading(false);
Review Comment:
On capability probe errors, the UI is forced into the same "not supported"
state as a true unsupported cluster (t('liteTopic.notSupported')). That message
tells users to upgrade to RocketMQ 5.x, which is misleading when the real
problem is that capability detection failed (backend/provider path
unavailable). Consider tracking a distinct "capability unavailable" state and
rendering a different Alert message (and i18n key) so users can distinguish
unsupported vs transient/backend failure.
--
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]
