| commit | 883ce21af30c0e1b331d749c4f20c63f3f5c36df | [log] [tgz] |
|---|---|---|
| author | Googler <wyv@google.com> | Wed Jul 06 10:01:59 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Jul 06 10:03:37 2022 -0700 |
| tree | f9b7a95dffc7fb89ec6348376bf6426185fa4ee6 | |
| parent | 8e03d82d83278ff29846dc1dba99382157d6f04c [diff] |
Add a conversionContext parameter to option converters We need to pass flag values through the repo mapping of the main repo, which means that at flag parsing time, we need access to the main repo mapping. To that end, we add a nullable untyped `conversionContext` parameter to the `Converter#convert` method, which is unused in this CL but will be used in a follow-up. Note that we can't directly add a `RepositoryMapping` parameter because the c.g.devtools.common.options package is a transitive dependency of c.g.devtools.build.lib.cmdline (which RepositoryMapping lives in). So this `conversionContext` will unfortunately need to be an Object. Reviewers: Please focus on reviewing changes in the c.g.devtools.common.options package. All the other changes in this CL are simply adding a `conversionContext` parameter to implementors of `Converter`, or passing this parameter to delegates, or superclasses. Work towards https://github.com/bazelbuild/bazel/issues/14852 PiperOrigin-RevId: 459278433 Change-Id: I98b3842305c34d2d0c33e7411c1024897fb0170a
{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
