mirror of
https://github.com/bevyengine/bevy
synced 2024-11-22 12:43:34 +00:00
rename example change_detection to have unique name (#2419)
# Objective Noticed a warning when running tests: ``` > cargo test --workspace warning: output filename collision. The example target `change_detection` in package `bevy_ecs v0.5.0 (/bevy/crates/bevy_ecs)` has the same output filename as the example target `change_detection` in package `bevy v0.5.0 (/bevy)`. Colliding filename is: /bevy/target/debug/examples/change_detection The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>. warning: output filename collision. The example target `change_detection` in package `bevy_ecs v0.5.0 (/bevy/crates/bevy_ecs)` has the same output filename as the example target `change_detection` in package `bevy v0.5.0 (/bevy)`. Colliding filename is: /bevy/target/debug/examples/change_detection.dSYM The targets should have unique names. Consider changing their names to be unique or compiling them separately. This may become a hard error in the future; see <https://github.com/rust-lang/cargo/issues/6313>. ``` ## Solution I renamed example `change_detection` to `component_change_detection`
This commit is contained in:
parent
b48ee02feb
commit
57c021538e
3 changed files with 3 additions and 3 deletions
|
@ -259,8 +259,8 @@ name = "ecs_guide"
|
||||||
path = "examples/ecs/ecs_guide.rs"
|
path = "examples/ecs/ecs_guide.rs"
|
||||||
|
|
||||||
[[example]]
|
[[example]]
|
||||||
name = "change_detection"
|
name = "component_change_detection"
|
||||||
path = "examples/ecs/change_detection.rs"
|
path = "examples/ecs/component_change_detection.rs"
|
||||||
|
|
||||||
[[example]]
|
[[example]]
|
||||||
name = "event"
|
name = "event"
|
||||||
|
|
|
@ -156,7 +156,7 @@ Example | File | Description
|
||||||
Example | File | Description
|
Example | File | Description
|
||||||
--- | --- | ---
|
--- | --- | ---
|
||||||
`ecs_guide` | [`ecs/ecs_guide.rs`](./ecs/ecs_guide.rs) | Full guide to Bevy's ECS
|
`ecs_guide` | [`ecs/ecs_guide.rs`](./ecs/ecs_guide.rs) | Full guide to Bevy's ECS
|
||||||
`change_detection` | [`ecs/change_detection.rs`](./ecs/change_detection.rs) | Change detection on components
|
`component_change_detection` | [`ecs/component_change_detection.rs`](./ecs/component_change_detection.rs) | Change detection on components
|
||||||
`event` | [`ecs/event.rs`](./ecs/event.rs) | Illustrates event creation, activation, and reception
|
`event` | [`ecs/event.rs`](./ecs/event.rs) | Illustrates event creation, activation, and reception
|
||||||
`fixed_timestep` | [`ecs/fixed_timestep.rs`](./ecs/fixed_timestep.rs) | Shows how to create systems that run every fixed timestep, rather than every tick
|
`fixed_timestep` | [`ecs/fixed_timestep.rs`](./ecs/fixed_timestep.rs) | Shows how to create systems that run every fixed timestep, rather than every tick
|
||||||
`hierarchy` | [`ecs/hierarchy.rs`](./ecs/hierarchy.rs) | Creates a hierarchy of parents and children entities
|
`hierarchy` | [`ecs/hierarchy.rs`](./ecs/hierarchy.rs) | Creates a hierarchy of parents and children entities
|
||||||
|
|
Loading…
Reference in a new issue