| commit | 214a5949291c5a45ff9cc2ad41d6e7508a73167a | [log] [tgz] |
|---|---|---|
| author | wyv <wyv@google.com> | Mon Sep 06 08:24:16 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Sep 06 08:25:41 2021 -0700 |
| tree | defbc0b9ebcdc5472de6e65cfbf25d848b7bf3ed | |
| parent | b5bbe28ce207375009babc142fd3e8ce915d3dc9 [diff] |
bzlmod: Types for module extension *evaluation* ================================================================= (https://github.com/bazelbuild/bazel/issues/13316) * `ModuleExtensionContext`: The `module_ctx` object to be passed to the module extension's implementation function. For now, it only has 1 extra property `modules` which allows the module extension to access the dependency graph and all relevant tags. * `StarlarkBazelModule`: The elements in `module_ctx.modules`. Each exposes the name and version of the module, and all the tags on it too. * `TypeCheckedTag`: The type-checked version of `Tag`, which is exposed to Starlark through `StarlarkBazelModule` above. It contains all the attribute values passed to it in tags, but also has everything converted to native types and back to Starlark (so strings in `Tag` could become Labels in `TypeCheckedTag`). PiperOrigin-RevId: 395101902
{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
