mirror of
https://github.com/bevyengine/bevy
synced 2024-11-23 05:03:47 +00:00
99c9218b56
# Objective Function reflection requires a lot of macro code generation in the form of several `all_tuples!` invocations, as well as impls generated in the `Reflect` derive macro. Seeing as function reflection is currently a bit more niche, it makes sense to gate it all behind a feature. ## Solution Add a `functions` feature to `bevy_reflect`, which can be enabled in Bevy using the `reflect_functions` feature. ## Testing You can test locally by running: ``` cargo test --package bevy_reflect ``` That should ensure that everything still works with the feature disabled. To test with the feature on, you can run: ``` cargo test --package bevy_reflect --features functions ``` --- ## Changelog - Moved function reflection behind a Cargo feature (`bevy/reflect_functions` and `bevy_reflect/functions`) - Add `IntoFunction` export in `bevy_reflect::prelude` ## Internal Migration Guide > [!important] > Function reflection was introduced as part of the 0.15 dev cycle. This migration guide was written for developers relying on `main` during this cycle, and is not a breaking change coming from 0.14. Function reflection is now gated behind a feature. To use function reflection, enable the feature: - If using `bevy_reflect` directly, enable the `functions` feature - If using `bevy`, enable the `reflect_functions` feature
22 lines
509 B
TOML
22 lines
509 B
TOML
[package]
|
|
name = "bevy_reflect_compile_fail"
|
|
edition = "2021"
|
|
description = "Compile fail tests for Bevy Engine's reflection system"
|
|
homepage = "https://bevyengine.org"
|
|
repository = "https://github.com/bevyengine/bevy"
|
|
license = "MIT OR Apache-2.0"
|
|
publish = false
|
|
|
|
[dependencies]
|
|
bevy_reflect = { path = "../", features = ["functions"] }
|
|
|
|
[dev-dependencies]
|
|
compile_fail_utils = { path = "../../../tools/compile_fail_utils" }
|
|
|
|
[[test]]
|
|
name = "derive"
|
|
harness = false
|
|
|
|
[[test]]
|
|
name = "func"
|
|
harness = false
|