Skip to content

Commit

Permalink
[7.3.0] Format "Repository names and strict deps" bullet list (bazelb…
Browse files Browse the repository at this point in the history
…uild#22679)

The bullet list in the "Repository names and strict deps" section of
https://bazel.build/external/module does not render properly on the
website. However, other bullet lists on this page do render correctly.
The difference is apparently the level of indentation. This PR attempts
to correct the discrepancy.

Closes bazelbuild#22663.

PiperOrigin-RevId: 641904379
Change-Id: I9d97841731ec99bad91796fff3fd3d62426b10ff

Commit
bazelbuild@f6687ad

Co-authored-by: David Sanderson <32687193+dws@users.noreply.github.com>
  • Loading branch information
bazel-io and dws authored Jun 10, 2024
1 parent 6f0e04c commit 3fea7d6
Showing 1 changed file with 12 additions and 12 deletions.
24 changes: 12 additions & 12 deletions site/en/external/module.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,18 +206,18 @@ multiple versions of the module in the entire dependency graph (see
Note that **the canonical name format** is not an API you should depend on and
**is subject to change at any time**. Instead of hard-coding the canonical name,
use a supported way to get it directly from Bazel:
* In BUILD and `.bzl` files, use
[`Label.repo_name`](/rules/lib/builtins/Label#repo_name) on a `Label` instance
constructed from a label string given by the apparent name of the repo, e.g.,
`Label("@bazel_skylib").repo_name`.
* When looking up runfiles, use
[`$(rlocationpath ...)`](https://bazel.build/reference/be/make-variables#predefined_label_variables)
or one of the runfiles libraries in
`@bazel_tools//tools/{bash,cpp,java}/runfiles` or, for a ruleset `rules_foo`,
in `@rules_foo//foo/runfiles`.
* When interacting with Bazel from an external tool such as an IDE or language
server, use the `bazel mod dump_repo_mapping` command to get the mapping from
apparent names to canonical names for a given set of repositories.
* In BUILD and `.bzl` files, use
[`Label.repo_name`](/rules/lib/builtins/Label#repo_name) on a `Label` instance
constructed from a label string given by the apparent name of the repo, e.g.,
`Label("@bazel_skylib").repo_name`.
* When looking up runfiles, use
[`$(rlocationpath ...)`](https://bazel.build/reference/be/make-variables#predefined_label_variables)
or one of the runfiles libraries in
`@bazel_tools//tools/{bash,cpp,java}/runfiles` or, for a ruleset `rules_foo`,
in `@rules_foo//foo/runfiles`.
* When interacting with Bazel from an external tool such as an IDE or language
server, use the `bazel mod dump_repo_mapping` command to get the mapping from
apparent names to canonical names for a given set of repositories.

[Module extensions](/external/extension) can also introduce additional repos
into the visible scope of a module.

0 comments on commit 3fea7d6

Please sign in to comment.