[BUG] API Document generation does not parse request parameters for RPC types (Dubbo/SOFA/TARS/gRPC)

[eye-gu]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The API document generation in ApiDocRegistrarImpl.getDocument() uses OpenApiUtils.generateDocumentParameters() for all RPC types without distinction. This method only supports parsing Spring Web annotations (@RequestParam, @RequestPart, path variables) for HTTP-style parameters. For non-HTTP RPC types (Dubbo, SOFA, TARS, gRPC), it fails to extract any meaningful request parameter information, since these RPC types do not use Spring Web annotations.

As a result, the generated API document for RPC types contains responseType (response details) but has empty/missing request parameter details — the document only has response, no request.

Expected Behavior

No response

Steps To Reproduce

No response

Environment

ShenYu version(s):

Debug logs

No response

Anything else?

No response

[github-actions]

👋 Hello @yuluo-yx

A new issue has been opened by @eye-gu:

• Title: [BUG] API Document generation does not parse request parameters for RPC types (Dubbo/SOFA/TARS/gRPC)
• Link: [BUG] API Document generation does not parse request parameters for RPC types (Dubbo/SOFA/TARS/gRPC) #6338

Please review when you have time. Thank you! 🙏

[damingqicai]

如何取消邮件发送，辛苦回复一下，谢谢 大明奇才 ***@***.*** 原始邮件 发件人：eye-gu ***@***.***> 发件时间：2026年5月12日 11:13 收件人：apache/shenyu ***@***.***> 抄送：Subscribed ***@***.***> 主题：[apache/shenyu] [BUG] API Document generation does not parse request parameters for RPC types (Dubbo/SOFA/TARS/gRPC) (Issue #6338) eye-gu created an issue (apache/shenyu#6338) Is there an existing issue for this?  I have searched the existing issues Current Behavior The API document generation in ApiDocRegistrarImpl.getDocument() uses OpenApiUtils.generateDocumentParameters() for all RPC types without distinction. This method only supports parsing Spring Web annotations ***@***.***, @RequestPart, path variables) for HTTP-style parameters. For non-HTTP RPC types (Dubbo, SOFA, TARS, gRPC), it fails to extract any meaningful request parameter information, since these RPC types do not use Spring Web annotations. As a result, the generated API document for RPC types contains responseType (response details) but has empty/missing request parameter details — the document only has response, no request. Expected Behavior No response Steps To Reproduce No response Environment ShenYu version(s): Debug logs No response Anything else? No response — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are subscribed to this thread.

[eye-gu]

@damingqicai 你是不是watching了shenyu？