Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Intellisense for Bazel projects with protos #479

Closed
Michaelhobo opened this issue Aug 6, 2020 · 3 comments
Closed

Intellisense for Bazel projects with protos #479

Michaelhobo opened this issue Aug 6, 2020 · 3 comments
Labels
FrozenDueToAge upstream-tools Issues that are caused by problems in the tools that the extension depends on.

Comments

@Michaelhobo
Copy link

Is your feature request related to a problem? Please describe.
I'm starting a Go project (https://github.com/Michaelhobo/nrfbazel) which uses protos. I have a library (nrfbazelify/nrfbazelify.go) which imports a local generated proto as "github.com/Michaelhobo/nrfbazel/bazelifyrc" - this import path is from a go_proto_library Bazel rule. Since this doesn't resolve to anything, I get an import error that shows up under the bazelifyrc import, and intellisense for the import is broken.

Describe the solution you'd like
Ideally, I'd like the language server to support Bazel - use Bazel to build targets, and pull intellisense data from there. I could also stop putting all my dependencies in a separate go.mod just for vscode.

Describe alternatives you've considered
Is there some workaround for pointing the proto to a local proto file? I'd have to generate the Go code and store it somewhere though, not sure how easy that is. Is there any tooling around to do something like this?

@hyangah
Copy link
Contributor

hyangah commented Aug 6, 2020

cc @stamblerre

@stamblerre
Copy link
Contributor

There is an issue tracking this work for gopls: golang/go#37205. The language server will work once there is a Bazel gopackagesdriver (bazel-contrib/rules_go#512).

@hyangah
Copy link
Contributor

hyangah commented Aug 18, 2020

Closing in favor of the issues in the upstream repos.

@hyangah hyangah added the upstream-tools Issues that are caused by problems in the tools that the extension depends on. label Aug 18, 2020
@hyangah hyangah closed this as completed Aug 18, 2020
@golang golang locked and limited conversation to collaborators Aug 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge upstream-tools Issues that are caused by problems in the tools that the extension depends on.
Projects
None yet
Development

No branches or pull requests

4 participants