gapic-generator-python
gapic-generator-python copied to clipboard
Generate Python API client libraries from Protocol Buffers.
Some of the inner READMEs, such as [this one](https://github.com/googleapis/google-cloud-python/blob/adea041c1d43b94d11ff9d4d5ba13c0d7898cac2/packages/google-cloud-speech/google/cloud/speech_v1/services/speech/transports/README.rst?plain=1#L2), are not rendered as intended. We need to fix the RST.
Update the logging section of README to refer to a generated library name instead of referring to a generic `library` name.
In the current version of #2270, the `httpResponse.payload` field is over-stringified: it's a single string with string-encoded JSON, rather than JSON object with the various fields. Since the response is...
Update showcase to test metadata with bytes and add a unit test to confirm this behaviour.
Extra fields are only included in the structured log format. We can update the code to append these extra fields directly in the message so that they appear if a...
We should be able to add a Github action to flag when there are spelling mistakes in pull requests. It's not clear which tool we should use for spell checking...
Generating the GAPIC for compute alpha (using the [disco-to-proto3 converter](https://github.com/googleapis/disco-to-proto3-converter) to create proto3s from the [Discovery file](https://www.googleapis.com/discovery/v1/apis/compute/alpha/rest)) results in a `RecursionError: maximum recursion depth exceeded while calling a Python object`....
We check the type of request / response i.e. `proto.Message` or `google.protobuf.message.Message` to appropriately convert the message to json. investigate if there's a better way or if we should simply...
We're logging rest headers as part of the http response and separately as a metadata field. This seems repetitive and needs to be cleaned up.
Investigate and add a debug log event before intercepting a `REST`. Look for this issue number to find where to add this log event.