Hong Zhang

Recently, Google updated the gRPC Transcoding spec, aka `google.api.http` annotation, to allow repeated field and mapped field as HTTP request/response body. This is to allow third party implementations, such as...

I worked on proto3, gRPC, and Google API Design Guide. This is a well known feature request. I would recommend gRPC Gateway implement this feature. When you perform a partial...

Good point. We should use a separate header for it.

@adematte I think you are correct. Google API Design Guide recommends every PATCH method has an `update_mask` in the request message. We can auto populate it. The request message should...

The streaming support can be added using a wrapper message, such as: ``` // A wrapper for (stream Foo) message StreamFoo { repeated Foo messages = 1; Status status =...

The entire response must be a valid JSON object, including the messages and the trailer. Otherwise, it won't be compatible with OpenAPI, and create all kind of compatibility issues. Incremental...

If you only send the array, where do you put the trailer? Adding the object wrapper does not add any complexity to the parser. The output looks like this: ```...

Changing between repeated and non-repeated is a breaking change for JSON. That is how JSON works, array of ints is different from int.

unary vs streaming is a breaking change in practice, just like repeated vs non-repeated. Let's not pretend otherwise. Even it doesn't break wire, it would certainly break client. You can...

The proposed the trailer support requires a few lines of code. The question is whether there is enough value to provide it at little cost? We can omit it for...