v0.25.1

Bug Fixes

• only require dataclases if python<3.7 (#475) (9597695)

v0.25.0

Features

• provide AsyncIO support for generated code (#365) (305ed34)

v0.24.2

Bug Fixes

• generated unit tests live in the 'tests/gapic' subdir (#456) (1ed7c9d), closes #454

v0.24.1

Bug Fixes

• update GOOGLE_API_USE_MTLS value (#453) (7449ad5)

gapic-generator 0.24.0

Features

• Add routing headers for non client streaming method calls
• Very early incomplete support for proto3 optional

Docs

• Add documentation describing how to invoke the microgenerator via Bazel

Bugfixes

• Disambiguate mtls semantics
• Resource helper method order stabilized in output

Testing

• Add systest for resource path parsing
• Add systest for non slash-delimited resource paths

Misc

• Remove lazy import in non ads-templates

gapic-generator 0.23.0

Features

• Add an opt_args parameter to the py_gapic_library Bazel rule
• The docker image uses the latest version of api-common-protos

Bugfixes

• Template directories paths are turned into absolute paths

gapic-generator 0.22.0

Bugfixes

• Fix for bazel rule in a Python 3.6 environment
• Adjust dependency requirements
• Clean up and fix lazy import for alternative templates
• All messages and enums are exported by top level (versionless) and versioned module views

Testing

• Lazy import is properly tested

gapic-generator 0.21.1

Bugfixes

• Fixes a minor lint issue
• Adds the MarkupSafe Bazel rule dependency

gapic-generator 0.21.0

Features

• Add a parallel set of templates for https://github.com/googleads/google-ads-python/
• Add mutual TLS support
• Implement resource path parsing methods in generated clients

Bugfixes

• Adds type annotation for a nested function
• Option parsing ignores whitespace after tokenization

Documentation

• Removed proof of concept and updated ownership in README.md

gapic-generator 0.20.0

Features

• Add support for building GAPICs with Bazel
• Add a naming workaround for certain APIs that require alternative directory structures

Bugfixes

• Generated unit tests that check method flattening properly handle deeply nested fields
• Map fields are properly handled in generated unit tests
• Client classes now have helper functions for resources nested deeply in the request message
• Messages with enum fields whose type is defined subsequently are handled correctly

Documentation

• The Getting Started documentation correctly describes client default instantiation