| commit | b3602eb14cf27494a0a754bc215ec2b94d13d89b | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Mon Jun 05 13:22:02 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Jun 05 13:23:22 2023 -0700 |
| tree | fcfac292c68a9c59243ed019e80ce6e422db98c7 | |
| parent | 276514bdb22b974913db79853ba1effd7a780866 [diff] |
Export the original file and symbol of documented entities in starlark_doc_extract It is a common pattern for modules to load a symbol (e.g. a rule or a provider) from an internal implementation module and then re-export it inside a struct namespace or even under a different name entirely. For building doc cross- references, we want to be able to uniquely identify symbols, so in addition to the names used inside a given module, we should export the moral equivalent of the symbols' keys / fingerprints - the file where the symbol was originally exported, and the name under which it was exported there. Also take the opportunity to document advertised providers for rules. As part of this change, we ought to have renamed ProviderNameGroup to something like ProviderReferenceGroup; unfortunately, that would break existing Stardoc markdown formatting templates, which require us to stay compatible with the existing java proto API. PiperOrigin-RevId: 537964225 Change-Id: Icb4c40448952edf7bbf93c5ddd616c26980dccf7
{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
