Frun1na opened a new issue, #4728:
URL: https://github.com/apache/rocketmq-dashboard/issues/4728
### Which Documentation
`docs/api-spec.md` — §6.2 消费组客户端, §14.1 通用设置, and the enum appendix (客户端语言 /
LLM 提供商 rows).
### What Is Wrong
Three places name values the API does not define:
1. **§6.2 protocol** — documented as `REMOTING` / `GRPC`. The `Protocol`
enum is `gRPC, Remoting`,
and the enum appendix of the same document already says `gRPC`,
`Remoting`, so §6.2 contradicts
both the code and itself.
2. **Appendix client languages** — the row lists the UI display labels
`C++`, `C#`, `Node.js`.
`ClientLanguage` is `Java, Go, Python, Rust, Cpp, CSharp, NodeJS, PHP`,
which is what
`ClientConnectionVO.language` returns on the wire; the UI maps those
values to the labels
(`web/src/pages/cluster/clients.tsx`). Every other appendix row lists
persisted values, so this
row should too.
3. **LLM providers (§14.1 and appendix)** — both list `openai` / `azure` /
`ollama` / `qwen`.
`LlmConfigService.PROVIDER_MODELS` defines `openai`, `azure`,
`anthropic`, `deepseek`, `tongyi`,
`ollama`, `bedrock`. `qwen` is a model name under `tongyi`, not a
provider key, so the documented
list both names a provider that does not exist and omits four that do.
### Suggested Change
Use the values the enums and `LlmConfigService` actually define; the UI-only
display labels stay in
the UI.
Opened PR #4727 for this.
--
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]
