You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Does this issue reproduce with the latest releases of all the above?
yes
What operating system and processor architecture are you using?
all
What did you do?
Add a go.mod which contains both .proto and .pb.go files, via go_deps.
What did you expect to see?
No protoc generation, generated BUILD files should reference the pb.go file.
What did you see instead?
When gazelle encounters .proto files it generates BUILD rules that compile the protos. This creates both a unexpected dependency on protoc, slower setup, and build experiences.
The text was updated successfully, but these errors were encountered:
stefanpenner
pushed a commit
to stefanpenner/bazel-gazelle
that referenced
this issue
May 7, 2024
What version of gazelle are you using?
Latest (0.35)
What version of rules_go are you using?
latest (0.44)
What version of Bazel are you using?
Latest (7.0.0)
Does this issue reproduce with the latest releases of all the above?
yes
What operating system and processor architecture are you using?
all
What did you do?
Add a go.mod which contains both
.proto
and.pb.go
files, via go_deps.What did you expect to see?
No protoc generation, generated BUILD files should reference the
pb.go
file.What did you see instead?
When gazelle encounters
.proto
files it generates BUILD rules that compile the protos. This creates both a unexpected dependency on protoc, slower setup, and build experiences.The text was updated successfully, but these errors were encountered: