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

Use apparent repo names when fixing loads #1321

Merged
merged 2 commits into from
Jan 10, 2025

Conversation

fmeum
Copy link
Contributor

@fmeum fmeum commented Jan 10, 2025

Whether a load for e.g. proto rules should be from @com_google_protobuf, @protobuf or a fully custom name depends on the repo_name on the bazel_dep for the protobuf module in the root module's module file.

This PR scans MODULE.bazel and included *.MODULE.bazel files for bazel_deps and uses the derived mapping for the suggested loads.

Whether a load for e.g. proto rules should be from `@com_google_protobuf`, `@protobuf` or a fully custom name depends on the `repo_name` on the `bazel_dep` for the `protobuf` module in the root module's module file.

This PR scans `MODULE.bazel` and included `*.MODULE.bazel` files for `bazel_dep`s and uses the derived mapping for the suggested loads.
@fmeum
Copy link
Contributor Author

fmeum commented Jan 10, 2025

@vladmos @Wyverald Would be great to get this out into an 8.0.1, otherwise many users will pick up load fixes that don't work for them.

@fmeum
Copy link
Contributor Author

fmeum commented Jan 10, 2025

FYI @comius

@vladmos vladmos merged commit 13fa613 into bazelbuild:main Jan 10, 2025
2 checks passed
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 this pull request may close these issues.

3 participants