| commit | 09a3ec9408da18351b351fde601b2c357c359d95 | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Thu Jun 08 17:56:53 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Jun 08 17:58:17 2023 -0700 |
| tree | f8259fa14c6e38e8ae112ae203fd6f6c288c64c3 | |
| parent | 1590dbc4be2ce262ee9348e12cdb44c3b6ee0544 [diff] |
Emit consistent names for providers in starlark_doc_extract If a module re-exports a provider in a namespace or under a different name, and that provider is also referred to by a rule or rule attribute, we should use the exported provider name consistently throughout our doc output (note that we also output the OriginKey message with the name under which the provider was exported in its original module). This requires processing a module's docs in two phases: first, collect all documentable providers' names and keys; and then process all documentable symbol documentation as before, using the providers' exported names when emitting rule docs. In turn, that means refactoring ModuleInfoExtractor to use a common abstraction (GlobalsVisitor) for recursively walking namespaced Starlark values in both phases. Also remove the rewriteWorkspace call in originKeyFileAndModuleInfoFileLabels which was accidentally added in the previous change. PiperOrigin-RevId: 538939476 Change-Id: I33565966019673b58caa134e676900ba16d09412
{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
