Aias00 opened a new issue, #795:
URL: https://github.com/apache/rocketmq-dashboard/issues/795
### Problem
The LiteTopic page currently assumes LiteTopic is supported when the
capability probe fails.
Current behavior in `web/src/pages/studio/LiteTopic.tsx`:
```ts
try {
const capability = await queryLiteTopicCapability();
...
} catch {
// Assume supported when capability detection is unavailable.
}
await fetchData(...)
```
If `/api/liteTopic/capability` is unavailable or returns an error, the page
continues to query LiteTopic list/quota data and renders the management surface
as if the feature is available.
### Expected behavior
Capability detection should fail closed. If Studio cannot confirm LiteTopic
support, the page should stop loading LiteTopic data and show an explicit
unavailable/unsupported state instead of enabling the management UI.
### Impact
This avoids misleading users into thinking LiteTopic management is available
when the backend/provider path is unhealthy or not implemented yet. It is
related to META-01 LiteTopic management in the RocketMQ Studio scope.
### Suggested fix
- On capability probe failure, clear LiteTopic data, stop loading, and
render the unavailable state.
- Add a regression test proving list/quota APIs are not called after
capability detection fails.
--
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]
