| commit | e33c2d14728aea6914b165fe11f08ff4982196ca | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Wed Jul 12 08:00:50 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 12 08:02:11 2023 -0700 |
| tree | 084c96ca27310faeb5242a023e59cd85a06f3c4e | |
| parent | 22a5d6df216fd7b5bb8ca8932118057c60874124 [diff] |
starlark_doc_extract: document repository rules and module extensions We introduce new message types in the proto for repository rules and for module extensions. Note that this is a behavioral change compared to the legacy Stardoc extractor, which extracted repository rule docs using RuleInfo messages (i.e. same as ordinary rules) - which was very likely to lead to reader confusion. ModuleExtensionInfo messages for now get an OriginKey field without the original name because ModuleExtension objects are not StarlarkExportable values, so finding the name under which a ModuleExtension was originally defined means searching through its defining module's globals (assuming it is in globals - it may not be). This will be added as a follow-up, but is low priority (due to the lower probability of name collisions for module extensions as compared to e.g. providers and rules) and should not block the ability to document module extensions in the first place. PiperOrigin-RevId: 547496231 Change-Id: I1ecb7f9b8bf2b7be78e565cb03a57d7227cda58f
{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
