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
That means the documentation for various IDE settings (and I assume other bits?) will have to change. It would be nice to have some prettier, more stable alias for the GOROOT and similar things needed. I'm not sure how much power bazel provides for this, though, so it's possible this ticket just needs to be closed or turned into a update-the-docs-when-change-lands ticket.
The text was updated successfully, but these errors were encountered:
I would like to recommend using https://github.com/buildbuddy-io/bazel_env.bzl instead of maintaining something like this in rules_go. It's still a somewhat new ruleset, but please give it a try and provide feedback.
Hm, I'm not sure how to make that work in the configuration of vscode workspaces, and so on where I would need it for my aliasing. Using an extension that loads direnv doesn't seem to work because it wouldn't necessarily fire before the Go extension settings are loaded.
In Bazel 8.0, the path separator will change from
~
to+
. (See the 7.3.0 release notes and associated PR)That means the documentation for various IDE settings (and I assume other bits?) will have to change. It would be nice to have some prettier, more stable alias for the GOROOT and similar things needed. I'm not sure how much power bazel provides for this, though, so it's possible this ticket just needs to be closed or turned into a update-the-docs-when-change-lands ticket.
The text was updated successfully, but these errors were encountered: