> Curious wouldn't `go run` give you the same? We use protobufs and pggen. Bazel transparently manages the codegen from proto file to Go code. > would you say

> Curious wouldn't `go run` give you the same? We use protobufs and pggen. Bazel transparently manages the codegen from proto file to Go code. > would you say your experience with golang IDEs / gopls is degraded? Yes, that's our biggest pain point with Go and Bazel. I haven't been able to coax IntelliJ into debugging Bazel managed binaries. To enable IntelliJ code analysis, we copy the generated code into the src directory (with a Bazel rule auto-generated by Gazelle) but don't add it to Git. I've tried the IntelliJ with Bazel plugin a few times but I've always reverted back to stock IntelliJ.