Tim Burks

I'm also experiencing this with fresh builds on two platforms (MacOS and Ubuntu). My Java versions are 1.8.0_151 (MacOS) and 1.8.0_222 (Ubuntu).

I think opposition to this is resulting from a particular way of thinking about API descriptions. Many OpenAPI descriptions are what I'll call **derivative**: they are generated from service implementations...

Here is [a specific proposal](https://github.com/OAI/OpenAPI-Specification/issues/1459) to address this. It supports current AWS API Gateway usage and a large class of Google APIs that are currently unsupportable by OpenAPI.

We would like to also be able to mark an entire API as deprecated. Repeating some internal discussion: The simplest change to support this would be to add the "deprecated"...

Here's a PR (#9) where I added Google Fonts support, hopefully in a non-breaking way, by passing a `TextStyle`-producing function into the `TerminalStyle` constructor. If passing in a `TextStyle` would...

Hi, I agree. I'm happy to share my RadMongoDB repo but don't have the time or resources to support it for third-party use. I think Paul will also be much...

It seems likely that there will be multiple transcoding implementations used within Google (if there aren't already) and third-party implementations also seem likely, so defining the mapping in an implementation-independent...

Here's a [draft](https://github.com/grpc/grpc.github.io/wiki/Mapping) that I wrote by starting with the comments in [http.proto](https://github.com/googleapis/googleapis/blob/master/google/api/http.proto) and trying to approach the point of view of REST API authors.

Other structures for this would be fine, but after rereading my draft I don't think the draft goes far enough in empathizing with REST service creators. That explanation (and any...

@jjkoh95 If you use `google.api.HttpBody` as your request message ([as illustrated here](https://github.com/googleapis/googleapis/blob/49dd2981f58dc88e8b9e76c726046584541287ed/google/api/httpbody.proto#L54)), then you can post arbitrary data to your transcoded RPC. This is supported by [Envoy](https://github.com/envoyproxy/envoy/pull/10110) and possibly other...