commit 63a73ac7f003bf72b6a109eb2634ddb9ae3ad3fb
author Amelia <140295624+AmeliasCode@users.noreply.github.com> Fri Feb 09 07:26:34 2024 -0800
committer GitHub <noreply@github.com> Fri Feb 09 15:26:34 2024 +0000
tree 082023e9a6d8c6c02127ed7b3e1f880d7cce9712
parent 7ce81c1e28c0eedffda2b61fa14ce223016054f8

Add support for `all_crate_deps` when using bzlmod (#2461)

This adds support for the `all_crate_deps` functionality in repositories
created via bzlmod. An [earlier
update](https://github.com/bazelbuild/rules_rust/pull/1910/files) that
added support for 3rd party crates with bzlmod intentionally left this
functionality out.

Some key things that I think should be reviewed: 

- Is the method of getting `crate_label_template` in `extensions.bzl`
the best approach? It requires a lot of hard-coding, and it seems like
it might be possible to simplify but I'm not familiar enough with the
code base to know how.
- Is the `generate_config_file` method from `crates_vendor.bzl` the
right method to use for generating the cargo-bazel config? It seems like
there are two places with similar logic (here and in
`crates_repositories.bzl` (see
https://github.com/bazelbuild/rules_rust/pull/1832)