bevy/docs
Alice Cecile 2fbb4c68ae
Define a prelude for bevy_color, and add it to bevy_internal (#12158)
# Objective

As we start to migrate to `bevy_color` in earnest (#12056), we should
make it visible to Bevy users, and usable in examples.

## Solution

1. Add a prelude to `bevy_color`: I've only excluded the rarely used
`ColorRange` type and the testing-focused color distance module. I
definitely think that some color spaces are less useful than others to
end users, but at the same time the types used there are very unlikely
to conflict with user-facing types.
2. Add `bevy_color` to `bevy_internal` as an optional crate.
3. Re-export `bevy_color`'s prelude as part of `bevy::prelude`.

---------

Co-authored-by: Alice Cecile <alice.i.cecil@gmail.com>
2024-02-27 17:04:56 +00:00
..
cargo_features.md Define a prelude for bevy_color, and add it to bevy_internal (#12158) 2024-02-27 17:04:56 +00:00
debugging.md Useful changes with relicensing benefits (#2497) 2021-07-17 21:59:31 +00:00
linters.md Allow clippy::type_complexity in more places. (#9796) 2023-10-02 21:55:16 +00:00
linux_dependencies.md add libxkbcommon-x11-0 to the default linux dependencies (#11060) 2023-12-21 23:14:05 +00:00
profiling.md fix link to tracy (#11521) 2024-01-27 19:23:37 +00:00
release_checklist.md Add a release step, add links to the github release note (#12041) 2024-02-23 18:36:07 +00:00
the_bevy_organization.md Run markdownlint (#11386) 2024-01-17 14:27:28 +00:00