d70595b667
# Objective - Fixes #6370 - Closes #6581 ## Solution - Added the following lints to the workspace: - `std_instead_of_core` - `std_instead_of_alloc` - `alloc_instead_of_core` - Used `cargo +nightly fmt` with [item level use formatting](https://rust-lang.github.io/rustfmt/?version=v1.6.0&search=#Item%5C%3A) to split all `use` statements into single items. - Used `cargo clippy --workspace --all-targets --all-features --fix --allow-dirty` to _attempt_ to resolve the new linting issues, and intervened where the lint was unable to resolve the issue automatically (usually due to needing an `extern crate alloc;` statement in a crate root). - Manually removed certain uses of `std` where negative feature gating prevented `--all-features` from finding the offending uses. - Used `cargo +nightly fmt` with [crate level use formatting](https://rust-lang.github.io/rustfmt/?version=v1.6.0&search=#Crate%5C%3A) to re-merge all `use` statements matching Bevy's previous styling. - Manually fixed cases where the `fmt` tool could not re-merge `use` statements due to conditional compilation attributes. ## Testing - Ran CI locally ## Migration Guide The MSRV is now 1.81. Please update to this version or higher. ## Notes - This is a _massive_ change to try and push through, which is why I've outlined the semi-automatic steps I used to create this PR, in case this fails and someone else tries again in the future. - Making this change has no impact on user code, but does mean Bevy contributors will be warned to use `core` and `alloc` instead of `std` where possible. - This lint is a critical first step towards investigating `no_std` options for Bevy. --------- Co-authored-by: François Mockers <francois.mockers@vleue.com>
106 lines
3.3 KiB
Rust
Executable File
106 lines
3.3 KiB
Rust
Executable File
#![cfg_attr(docsrs, feature(doc_auto_cfg))]
|
|
#![forbid(unsafe_code)]
|
|
#![doc(
|
|
html_logo_url = "https://bevyengine.org/assets/icon.png",
|
|
html_favicon_url = "https://bevyengine.org/assets/icon.png"
|
|
)]
|
|
|
|
//! Parent-child relationships for Bevy entities.
|
|
//!
|
|
//! You should use the tools in this crate
|
|
//! whenever you want to organize your entities in a hierarchical fashion,
|
|
//! to make groups of entities more manageable,
|
|
//! or to propagate properties throughout the entity hierarchy.
|
|
//!
|
|
//! This crate introduces various tools, including a [plugin]
|
|
//! for managing parent-child relationships between entities.
|
|
//! It provides two components, [`Parent`] and [`Children`],
|
|
//! to store references to related entities.
|
|
//! It also provides [command and world] API extensions
|
|
//! to set and clear those relationships.
|
|
//!
|
|
//! More advanced users may also appreciate
|
|
//! [query extension methods] to traverse hierarchies,
|
|
//! and [events] to notify hierarchical changes.
|
|
//! There is also a [diagnostic plugin] to validate property propagation.
|
|
//!
|
|
//! # Hierarchy management
|
|
//!
|
|
//! The methods defined in this crate fully manage
|
|
//! the components responsible for defining the entity hierarchy.
|
|
//! Mutating these components manually may result in hierarchy invalidation.
|
|
//!
|
|
//! Hierarchical relationships are always managed symmetrically.
|
|
//! For example, assigning a child to an entity
|
|
//! will always set the parent in the other,
|
|
//! and vice versa.
|
|
//! Similarly, unassigning a child in the parent
|
|
//! will always unassign the parent in the child.
|
|
//!
|
|
//! ## Despawning entities
|
|
//!
|
|
//! The commands and methods provided by `bevy_ecs` to despawn entities
|
|
//! are not capable of automatically despawning hierarchies of entities.
|
|
//! In most cases, these operations will invalidate the hierarchy.
|
|
//! Instead, you should use the provided [hierarchical despawn extension methods].
|
|
//!
|
|
//! [command and world]: BuildChildren
|
|
//! [diagnostic plugin]: ValidParentCheckPlugin
|
|
//! [events]: HierarchyEvent
|
|
//! [hierarchical despawn extension methods]: DespawnRecursiveExt
|
|
//! [plugin]: HierarchyPlugin
|
|
//! [query extension methods]: HierarchyQueryExt
|
|
|
|
extern crate alloc;
|
|
|
|
mod components;
|
|
pub use components::*;
|
|
|
|
mod hierarchy;
|
|
pub use hierarchy::*;
|
|
|
|
mod child_builder;
|
|
pub use child_builder::*;
|
|
|
|
mod events;
|
|
pub use events::*;
|
|
|
|
mod valid_parent_check_plugin;
|
|
pub use valid_parent_check_plugin::*;
|
|
|
|
mod query_extension;
|
|
pub use query_extension::*;
|
|
|
|
/// The hierarchy prelude.
|
|
///
|
|
/// This includes the most common types in this crate, re-exported for your convenience.
|
|
pub mod prelude {
|
|
#[doc(hidden)]
|
|
pub use crate::{child_builder::*, components::*, hierarchy::*, query_extension::*};
|
|
|
|
#[doc(hidden)]
|
|
#[cfg(feature = "bevy_app")]
|
|
pub use crate::{HierarchyPlugin, ValidParentCheckPlugin};
|
|
}
|
|
|
|
#[cfg(feature = "bevy_app")]
|
|
use bevy_app::prelude::*;
|
|
|
|
/// Provides hierarchy functionality to a Bevy app.
|
|
///
|
|
/// Check the [crate-level documentation] for all the features.
|
|
///
|
|
/// [crate-level documentation]: crate
|
|
#[cfg(feature = "bevy_app")]
|
|
#[derive(Default)]
|
|
pub struct HierarchyPlugin;
|
|
|
|
#[cfg(feature = "bevy_app")]
|
|
impl Plugin for HierarchyPlugin {
|
|
fn build(&self, app: &mut App) {
|
|
app.register_type::<Children>()
|
|
.register_type::<Parent>()
|
|
.add_event::<HierarchyEvent>();
|
|
}
|
|
}
|