higress-group/higress

Dubbo协议转换的参数匹配

Open

#498 opened on Aug 24, 2023

View on GitHub
 (11 comments) (0 reactions) (1 assignee)Go (1,219 forks)github user discovery
area/dubbogood first issuesig/controller

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

目前看代码和文档，发现http请求转换到dubbo接口上的参数，是根据参数顺序来的，而和dubbo接口上参数的名称无关。 这样设计有什么原因吗？感觉有些反直觉。

另外我如果希望把一整个json body都塞进一个map里（没有paramkey），有办法实现吗？ 例如 { "a":1, "b":2 } 这样的jsonbody，转成一个包含两个entry的map。

Contributor guide

Research direction
Examine the Dubbo protocol conversion code in the repository to understand how HTTP request parameters are mapped to Dubbo service arguments. Look for the logic that extracts parameters by order and the possibility of mapping by name or passing entire JSON body as a map.
Tech stack
go
Domain
backendapi
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoHTTPDubbo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60