| commit | b77e8c2a99ab37b8ef58f08a29f1e703ec15a246 | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Tue Apr 11 14:24:51 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Apr 11 14:26:15 2023 -0700 |
| tree | 45f70d6ec714e9364d98b519922abc53a92509ed | |
| parent | 1b4a0f0be81c8ccb9745303984cb5157b048bab0 [diff] |
starlark_doc_extract: stringify label-valued default attribute values For human-readable docs, want to stringify labels in a way that (1) elides the name part when unambiguous, matching buildifier behavior; and (2) respects repo mapping, so we don't print full bzlmod canonical repo names. Unfortunately, this means introducing yet another stringification method to Label, which combines the behavior of getDisplayForm() and toShorthandString() but cannot be conveniently composed from them. Alas. PiperOrigin-RevId: 523504039 Change-Id: Ia09ebb77cff09aaeb270f43ed7e319c90a44aa52
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
