Reflect and register Collider type

[timothee-haudebourg]

Hi, I'm blocked because the Collider type is not registered to the app, and cannot be manually registered because it lacks the required traits implementations. I guess it is related to this TODO:

bevy_rapier/src/geometry/collider.rs

Line 61 in af5ac6e

#[derive(Component, Clone)] // TODO: Reflect

I suppose this is not the only type that requires reflection. Is there any work in progress to add those? If not I may write a PR.

[Aceeri]

This currently requires some changes on bevy_reflect side as Compound is a self-referential type, I would suggest using https://github.com/devildahu/bevy_mod_component_mirror for now, but know that it will be a subset of the available collider types.

[Luminoth]

it looks like the linked PR has been merged, is the door opened now to impl Reflect on Collider? The space editor project has a requirement on that for Components.

[janhohenheim]

Semi-relevant issue: dimforge/rapier#467

[Zeenobit]

The HEAD revision of moonshine-save now supports "component mappers" to solve this issue as a workaround.

It's a similar idea to component mirror, but baked into the save pipeline:

app.register_type::<SerializedCollider>()
  .add_systems(
      PreUpdate,
      (
          save_default()
              .map_component(serialize_collider)
              .into_file("example.ron"),
          load_from_file_with_mapper(
              "example.ron",
              SceneMapper::default().map(deserialize_collider),
          ),
      ),
  )

Where serialize_collider and deserialize_collider are defined as:

#[derive(Component, Reflect)]
#[reflect(Component)]
enum SerializedCollider {
    Ball(f32),
    // ...
}

fn serialize_collider(collider: &Collider) -> SerializedCollider {
    if let Some(ball) = collider.as_ball() {
        SerializedCollider::Ball(ball.radius())
    } else {
        todo!()
    }
}

fn deserialize_collider(serialized: &SerializedCollider) -> Collider {
    match serialized {
        SerializedCollider::Ball(radius) => Collider::ball(*radius),
        _ => todo!(),
    }
}

I'm curious to know if:

1. Can every collider be serialized indirectly like this? If not, what subset of it could be?
2. Are there any other types in bevy_rapier that suffer from the same issue?