RockteMQ-AI commented on issue #4845: URL: https://github.com/apache/rocketmq-dashboard/issues/4845#issuecomment-5771041288
**Issue Evaluation** Category: `bug` | Status: **Confirmed** The reported issue has been verified against the current codebase (`rocketmq-studio` branch, commit `4c697f07`). **Root Cause:** `ClientLanguage` enum includes `NodeJS`, but `RocketMQClientProvider.mapLanguage` has no `LanguageCode` → `ClientLanguage.NodeJS` mapping in its switch statement. The `default` branch returns `null`, so Node.js client connections are published with `"language": null`. The frontend then renders an empty/unknown tag because `languageConfig[null]` has no match. This is the same underlying issue as #4849 but specifically about Node.js clients — the `mapLanguage` method needs a case for the Node.js `LanguageCode` (likely `LanguageCode.JAVASCRIPT` or similar) mapping to `ClientLanguage.NodeJS`. **Impact:** Node.js client connections show as "unknown" in the clients page, making it impossible to track Node.js SDK adoption. **Severity:** Medium — UI/display issue, no functional impact on message processing. **Suggested fix:** Add the missing `LanguageCode` → `ClientLanguage.NodeJS` case in `mapLanguage`. An automated fix proposal can be generated. Reply `/approve` to proceed with PR generation. --- *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]
