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
#480 will add the ability for update-repos to write repository rules to a macro in a separate .bzl file.
Gazelle currently reads repository rules declared in WORKSPACE in order to discover custom repository names and known prefixes. This information is used for dependency resolution. If repositories are declared in a macro, this information will no longer be available (though #132 would be a useful escape hatch).
We should have a directive that tells Gazelle to look for repository rules in a macro in a .bzl file. It should be possible to repeat this directive, since there may be multiple macros.
This is mainly useful for the fix and update commands, but bonus points if update-repos can update repository rules in the corresponding macros without additional command line arguments instead of writing copies to WORKSPACE.
The text was updated successfully, but these errors were encountered:
Soon, yes. #477 is the main release blocker. I've gotten sidetracked with some toolchain compatibility issues in new versions of Bazel, but I expect to come back to this soon.
#480 will add the ability for
update-repos
to write repository rules to a macro in a separate .bzl file.Gazelle currently reads repository rules declared in WORKSPACE in order to discover custom repository names and known prefixes. This information is used for dependency resolution. If repositories are declared in a macro, this information will no longer be available (though #132 would be a useful escape hatch).
We should have a directive that tells Gazelle to look for repository rules in a macro in a .bzl file. It should be possible to repeat this directive, since there may be multiple macros.
This is mainly useful for the
fix
andupdate
commands, but bonus points ifupdate-repos
can update repository rules in the corresponding macros without additional command line arguments instead of writing copies to WORKSPACE.The text was updated successfully, but these errors were encountered: