#7466 is the motivation for this and it should be expanded to all relevant languages.
Protobuf files can contain a packaging option that provides an explicit value or "hint" for code generators to use in "naming" the generated code. Our protoc plugin based GAPIC generators can consume this, but when it is used to inform the output directory and thus the file paths of files we need to encode elsewhere e.g. in release-please configuration, we librarian to understand it as well.
librarian add should be able to parse the .proto options - either on a per langauge basis or using some centralized lib for doing so - for use in librarian configuration and future implementation e.g. reference in generate.
Protobuf docs: https://protobuf.dev/programming-guides/proto3/#packages
AIP docs: https://google.aip.dev/191#packaging-annotations
#7466 is the motivation for this and it should be expanded to all relevant languages.
Protobuf files can contain a packaging option that provides an explicit value or "hint" for code generators to use in "naming" the generated code. Our
protocplugin based GAPIC generators can consume this, but when it is used to inform the output directory and thus the file paths of files we need to encode elsewhere e.g. in release-please configuration, we librarian to understand it as well.librarian addshould be able to parse the.protooptions - either on a per langauge basis or using some centralized lib for doing so - for use in librarian configuration and future implementation e.g. reference ingenerate.Protobuf docs: https://protobuf.dev/programming-guides/proto3/#packages
AIP docs: https://google.aip.dev/191#packaging-annotations