Open CristianNeamtu-47684 opened 3 weeks ago
Upon a closer inspection proto/protovalidate/buf/validate/validate.proto imports buf/validate/priv/private.proto
.
Is there another way we can enable others to generate code (without buf) while also providing/managing dependencies? For example: C#, Ruby
Hi,
Could you please let me know if there are any options to export the proto files as third_party/
dependencies?
This is useful for people that use @grpc/proto-loader or protoc
directly, where proto files need to be explicitly added to path.
Thank you!
Feature description: Set default package visibility to public for proto files since they can be seen as an api specification
Problem it solves or use case: A user of protovalidate may decide to provide their own protobuf definitions for others to use and to generate code based on them. With bazel this is more difficult because they are not publicly exported with the
github.com/bufbuild/protovalidate-go
.This can be worked around by either copying them in the 3rd party protos or copying them via a git_repository. With either option it's easy to be out of sync with the go dependency as time passes.
This is useful when working with other individuals or teams that have not transitioned to
buf
Proposed implementation or solution: Define default package visibility as public
Contribution: If approved and I can raise a pull-request with the abode change added to the BUILD.bazel
Examples or references: The deprecated
protoc-gen-validate
BUILD.bzazel Google APIs BUILD.bazelThese references allow shipping proto dependenices together with the user's proto definitions.
Additional context: Bazel query
Our usecase