We want per-service [^1] features so application developers can compile a subset of large crates, such as `google-cloud-aiplatform-v1`. - [x] Need option to create one feature per client - [x] Need to compute transitive closure of the messages, enums, etc. used by each client - [x] Need to gate each client by the corresponding feature - [x] Need to gate each message by the features of any client that needs them - [x] Need to document the features associated with each client in the README.md - [x] Need to document the features associated with each client `#[cfg_attr(docsrs, doc(cfg(feature = "blah blah blah")))]` - [x] googleapis/librarian#2560 [^1]: in this context a "service" is a "protobuf syntax service", which maps to a single `client::*` struct in our crates.
We want per-service 1 features so application developers can compile a subset of large crates, such as
google-cloud-aiplatform-v1.#[cfg_attr(docsrs, doc(cfg(feature = "blah blah blah")))]Footnotes
in this context a "service" is a "protobuf syntax service", which maps to a single
client::*struct in our crates. ↩