Add config() query function support to aquery (resolving #10872) This change enables the `config(expr, word)` function in `aquery` by: 1. Moving `ConfigFunction` from `cquery` package to `query2` package and generalizing its `eval()` method to work with any `PostAnalysisQueryEnvironment`. 2. Lifting `getConfiguredTargetsForConfigFunction` into `PostAnalysisQueryEnvironment<T>` so that both `cquery` and `aquery` share identical configuration resolution and error reporting. 3. Implementing `getConfiguredTarget(Label, BuildConfigurationValue)` and `getQueryName()` in both `ActionGraphQueryEnvironment` and `ConfiguredTargetQueryEnvironment`. 4. Registering `ConfigFunction` in `ActionGraphQueryEnvironment.AQUERY_FUNCTIONS`. 5. Adding unit tests for `config()` in `ActionGraphQueryTest`. 6. Adding integration tests for `config()` in `aquery_test.sh`. 7. Documenting `config()` in `devtools/blaze/docs_src/aquery.html`. RELNOTES: Aquery now supports the `config(expr, word)` function. PiperOrigin-RevId: 971764077 Change-Id: I7ead2ed2da603a228891493d800d8d12921ff3e0
{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.
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
