Provide defaults for optional CrateInfo fields in _create_crate_info (#4322)

Currently, `_create_crate_info` only provides defaults for a small
subset of the fields on the `CrateInfo` provider. If custom rules
instantiate `CrateInfo` using only the fields they care about, they are
susceptible to sudden runtime `AttributeError` crashes if `rules_rust`
internal logic is updated to unconditionally access a field that wasn't
previously required.

This PR adds defaults for all remaining non-essential fields in
`_create_crate_info` and the only fields left without defaults are the
strictly required semantic fields (`name` and `type`).

---------

Signed-off-by: Taylor Edwards <tayloredwards@google.com>
1 file changed
tree: 8c000ea47bdbfdcffb2e0e2c5399fe941f1c73bc
  1. .bazelci/
  2. .bcr/
  3. .github/
  4. cargo/
  5. crate_universe/
  6. docs/
  7. examples/
  8. extensions/
  9. ffi/
  10. nix/
  11. rust/
  12. test/
  13. tools/
  14. util/
  15. .bazelignore
  16. .bazelrc
  17. .clang-format
  18. .clippy.toml
  19. .envrc
  20. .gitattributes
  21. .gitignore
  22. .pre-commit-config.yaml
  23. .prettierrc.toml
  24. .rustfmt.toml
  25. .typos.toml
  26. ARCHITECTURE.md
  27. AUTHORS
  28. BUILD.bazel
  29. CODEOWNERS
  30. COMPATIBILITY.md
  31. CONTRIBUTING.md
  32. CONTRIBUTORS
  33. LICENSE.txt
  34. MODULE.bazel
  35. README.md
  36. version.bzl
  37. WORKSPACE.bazel
README.md

Rust Rules

  • Postsubmit Build status

Overview

This repository provides rules for building Rust projects with Bazel.

Starter repo

The fastest way to try this in an empty project is to click the green “Use this template” button on https://github.com/bazel-starters/rust.

Community

General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.

Documentation

Please refer to the full documentation.