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.