| commit | 51249ecc40487b6c2bd567342744cef46ad06ccc | [log] [tgz] |
|---|---|---|
| author | Googler <arostovtsev@google.com> | Mon May 01 12:36:10 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 01 12:37:42 2023 -0700 |
| tree | 5cc82b491d8776a9d99a5886a8dd9928669708b8 | |
| parent | 1a4da7f331c753c92e2c91efcad434dc29d10d43 [diff] |
Preserve Starlark field declaration order in StarlarkProvider.getSchema (former getSchemaWithDocumentation) We want the original field declaration order for starlark_doc_extract, both to match existing Stardoc behavior and to match existing logic of preserving the original declaration order of rule attributes etc. in proto output (leaving sorting up to the renderer). We want to take this opportunity to clean up StarlarkProvider's field and method names a little bit: * rename StarlarkProvider.schema to `fields` to emphasize that these are just the fields names, not the full schema given to the provider() call - it has a different iteration order and is missing doc strings - and to match the getFields() method name, logically enough * rename StarlarkProvider.getSchemaWithDocumentation to just getSchema - since it now returns the original schema from Starlark with the same order, and since the method may be used regardless of whether the schema is documented PiperOrigin-RevId: 528545413 Change-Id: I2756f4520c80acaca17dcd244b61d60aac5539b4
{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
