Support nested messages in GET request queries

描述

service MyService {
    rpc myMethod (myMethodRequest) returns (myMethodResponse) {
        option (google.api.http) = {
            get: "/method/all"
        };
    }
}

message myMethodRequest {
    repeated Scoped scope = 1;

    message Scoped {
        oneof condition {
            ById by_id = 1;
        }
        message ById {
            uint32 id = 1;
        }
    }
}

message myMethodResponse {
    repeated uint32 ids = 1;
}

localhost:8080/method/all?scope.by_id.id=3

unexpected repeated field in scope.by_id.id

贡献者指南

技术栈

gogrpcrest api

领域

apibackend

议题类型

feature

难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。

3

预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。

1-2 days

活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。

stale

清晰度议题是否清楚说明期望改动、验收标准和下一步。

clear

前置要求

GogRPCProtocol BuffersHTTP query parameter parsing

新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。

35

研究方向

Investigate the query parameter parsing logic in the grpc gateway's runtime package (likely `runtime/query.go`). The issue is that nested repeated messages within a `oneof` are not handled correctly when flattening query parameters. Examine how the gateway currently parses fields like `scope.by id.id` and why it triggers an 'unexpected repeated field' error. Look at the protobuf definition: `myMethodRequest.Scoped` contains a `oneof condition` with `ById`. The gateway should support `scope.by id.id` as a valid query parameter. Check existing tests for query parameter parsing to understand expected behavior. Consider how the gateway handles repeated fields (repeated Scoped scope) and nested messages. The solution likely involves modifying the parser to correctly traverse `oneof` fields and allow nested access. Review any comments or linked discussions in the issue for additional context.