| commit | 1f3baa25428f25a72d19d25423b6f675495fac8a | [log] [tgz] |
|---|---|---|
| author | Googler <cmita@google.com> | Thu Apr 25 10:36:02 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Apr 25 10:37:52 2024 -0700 |
| tree | 44cd75ff1976fbbdb1ca8ba2bfc937543695a071 | |
| parent | 618c0abbfe518f4e29de523a2e63ca9179050e94 [diff] |
Add the concept of "generic" rules to our Starlark's doc-gen. The documentation makes a distinction between "language-specific" and "language-agnostic" (or "generic") rules. It is an error for these to be different between rules within a "family" (if one is generic, they must all be generic). However, there is currently no way to mark a rule as "generic" in Starlark. So we check the "type" string that is parsed from the "doc-struct" and if it's generic, we flag it is as such. Generic rules always have their type set to "other" so there's no issue with overloading the string in this way. PiperOrigin-RevId: 628120344 Change-Id: I52e89448a653bd17b5501d42b6449c3fa8ad1d24
{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
