| commit | cf99f8476df4110ac749deda15340ebde74a2116 | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Mon Oct 03 08:31:34 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Oct 03 08:33:16 2022 -0700 |
| tree | b25bb4e6ea9e751bbaf3f8f3db8ff7d46a737bac | |
| parent | 0653d5fd78147871efa272d8979b080de150785c [diff] |
Allow native.existing_rule/s() with --incompatible_existing_rules_immutable_view to be encoded as json and passed as **kwargs To do so, we make ExistingRuleView and ExistingRulesView implement Map. This requires getting rid of NotRepresentableException in starlarkifyValue (see discussion in #13829) so that the view object's accessors don't throw. And that is, arguably, the correct thing to do: the distinction between returning null for some non-representable attributes vs. throwing an exception for others was entirely artificial. This in turn implies a small change in behavior: now, `existing_rule(x).keys()` will omit all attributes whose values cannot be represented in Starlark. (The old behavior was to allow some such attributes, and throw an exception when their value was accessed.) Fixes https://github.com/bazelbuild/bazel/issues/13829 Fixes https://github.com/bazelbuild/bazel/issues/16256 PiperOrigin-RevId: 478511532 Change-Id: If0c580a4e4eee1739136ea30eddce9eca71995e3
{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
