mirror of
https://github.com/bevyengine/bevy
synced 2024-11-10 07:04:33 +00:00
2fbb4c68ae
# 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> |
||
---|---|---|
.. | ||
cargo_features.md | ||
debugging.md | ||
linters.md | ||
linux_dependencies.md | ||
profiling.md | ||
release_checklist.md | ||
the_bevy_organization.md |