| commit | afb05cc96a039c58e6b9330add8eea52acebc111 | [log] [tgz] |
|---|---|---|
| author | Googler <hvd@google.com> | Fri Sep 08 03:38:51 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 08 03:40:18 2023 -0700 |
| tree | da166dc5ae7487948c0859678a273357ffa30d0d | |
| parent | 29bbad78c3a3a6edb1d3c80b760cc1622a35a686 [diff] |
Lift all subrule attributes to a rule that uses it. We just add the attributes defined on the subrules to the rule class as if they were defined on the rule itself (renaming them to avoid conflict). This seems to be the simplest way to leverage all the existing rule machinery to resolve dependencies *and* get the right results for `bazel query` A downside of doing it this way, is that it makes these attributes bona fide attributes of the rule. So if we want to ensure these attributes are not accessible via the rule context, it will require performing some extra checks. I haven't done that here and I'm not sure if that is worth it. The subrule proposal is meant to help make the code modular and have better abstractions. If one wishes to go the extra mile to violate that, :shrugs: PiperOrigin-RevId: 563703792 Change-Id: Ifdb0893208e3693a5cde473f0cfeb3d16583d402
{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
