-
Notifications
You must be signed in to change notification settings - Fork 317
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
Golang: Out of Sync / right-click test configurations #214
Comments
Thanks for the reply @chaoren, yeah I am missing those options. Let me see if I can create a reproducible example outside our private monorepo context. |
@chaoren, here is one of our public projects that I was able to repro the issue with: I setup the project via:
Via TestGetItemEmpty: Via BUILD |
Problem seems to be in rules_go. |
Thank you @chaoren 👍 ! |
Bad news. Those providers are not usable unless we load their definitions from the rules_go repo into our aspect, but we also run the aspect for non-go workspaces, and there's no such thing as a conditional load. We'll need to talk with the bazel people about potentially changing the providers API. |
Is the |
We're in discussions with the Skylark folks now to come up with a solution for this (likely adding support for a conditional load). The only reason our plugin currently works for java-like languages (java, scala, kotlin) is that the java providers we use are bundled with Bazel. This is something we're going to have to solve for all languages. |
It works as of the latest plugin and IDE. |
We are missing the right-click Run/Debug options in Golang projects that we have for Java/Scala.
We can execute tests form the corresponding BUILD file, but not from the context of the test file itself either as a whole unit or an individual method.
It also appears that the Workspace is frequently out-of-sync (via the light in the toolbar).
Sample
.bazelproject
:I am interesting in contributing, would we just need to port somethings over from the Java/Scala invocations?
The text was updated successfully, but these errors were encountered: