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

Gazelle should extract module mappings from imported foo.MODULE.bazel files #1804

Closed
mortenmj opened this issue May 18, 2024 · 0 comments · Fixed by #1810
Closed

Gazelle should extract module mappings from imported foo.MODULE.bazel files #1804

mortenmj opened this issue May 18, 2024 · 0 comments · Fixed by #1810

Comments

@mortenmj
Copy link
Contributor

mortenmj commented May 18, 2024

What version of gazelle are you using?

0.36.0

What version of rules_go are you using?

0.47.1

What version of Bazel are you using?

7.2.0rc1

Does this issue reproduce with the latest releases of all the above?

Yes

What operating system and processor architecture are you using?

Linux/AMD64

What did you do?

Moved rules_go import/setup to separate go.MODULE.bazel and imported from MODULE.bazel

What did you expect to see?

No changes to rules_go imports

What did you see instead?

When running Gazelle, imports from rules_go change from our apparent name to @@rules_go, e.g.:

+        "@@rules_go~//go/runfiles",
         "@com_github_stretchr_testify//suite",
-        "@io_bazel_rules_go//go/runfiles:go_default_library",
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant