Module missing_reflect

Checks for components, resources, and events that do not implement Reflect.

Motivation

Reflection lets programs inspect type information at runtime. It is commonly used by tools to view and edit ECS information while the program is running. Reflection is opt-in, however, and easy to forget since you need to #[derive(Reflect)] for each type that uses it.

Known issues

This lint will suggest #[derive(Reflect)] even if it cannot be applied. (E.g. if one of the fields does not implement Reflect.) For more information, please see #141.

Example

#[derive(Component)]
struct MyComponent;

Use instead:

// Remember to also register this component in the `App` type registry.
#[derive(Component, Reflect)]
struct MyComponent;

Often you’ll only want to enable this lint for a specific module:

mod types {
    #![cfg_attr(bevy_lint, warn(bevy::missing_reflect))]

    #[derive(Resource, Reflect)]
    struct Score(u32);

    #[derive(Component, Reflect)]
    struct Happiness(i8);
}

For more information, please see Toggling Lints in Code.

Structs

MissingReflect

Statics

MISSING_REFLECT

Click me for more information.