Add Convert<Option<TypeTagged>> and Convert<Vec<TypeTagged>>

[Shute052]

Would it be possible to add these Converters? I would really appreciate it. They are essential for

• Replace axis-like input configuration with new input processors Leafwing-Studios/leafwing-input-manager#494

[mintlu8]

I think these are entirely possible to be created by the user.
I'll see if I can come up with some good abstractions for these types.

[mintlu8]

The new ProjectOption and ProjectVec might fit this use case.

https://github.com/mintlu8/bevy_serde_project/releases/tag/0.2.0

[Shute052]

Thank you, but how do they work with TypeTagged? I'm curious! These are failed

#[serde_project("ProjectVec<Vec<TypeTagged<Box<dyn DualAxisProcessor>>>>")]
pub(crate) sequence: Vec<Box<dyn DualAxisProcessor>>,

#[serde_project("ProjectVec<Vec<Box<dyn DualAxisProcessor>>>")]
pub(crate) sequence: Vec<Box<dyn DualAxisProcessor>>,

[mintlu8]

The first field should be an exact copy of the Vec's type, the second field (optional) should be the projection of individual fields.

ProjectVec<Vec<Box<dyn DualAxisProcessor>>,  TypeTagged<Box<dyn DualAxisProcessor>>>"

[Shute052]

Yeah, that fixes the issue.

But it seems like I'm running into another problem with recursive dyn Traits. It looks like Serialize, Deserialize, and SerdeProject can't play nice together, and the generated __Ser is out of reach from the outside.

#[derive(Debug, Default, Clone, PartialEq, Eq, Hash, Reflect, Serialize, Deserialize, SerdeProject)]
pub struct DualAxisProcessingPipeline {
    #[serde_project(
        "ProjectVec<Vec<Box<dyn DualAxisProcessor>>, TypeTagged<Box<dyn DualAxisProcessor>>>"
    )]
    pub(crate) sequence: Vec<Box<dyn DualAxisProcessor>>,
}

impl DualAxisProcessor for DualAxisProcessingPipeline {
    /// Computes the result by passing the `input_value` through this pipeline.
    #[must_use]
    #[inline]
    fn process(&self, input_value: Vec2) -> Vec2 {
        self.sequence
            .iter()
            .fold(input_value, |value, next| next.process(value))
    }

    #[doc(hidden)]
    fn typetag_name(&self) -> &'static str {
        "DualAxisProcessingPipeline"
    }

    #[doc(hidden)]
    fn as_ser(&self) -> &dyn bevy::reflect::erased_serde::Serialize {
        self
    }
}

impl IntoTypeTagged<Box<dyn DualAxisProcessor>> for DualAxisProcessingPipeline {
    fn name() -> impl AsRef<str> {
        "DualAxisProcessingPipeline"
    }

    fn into_type_tagged(self) -> Box<dyn DualAxisProcessor> {
        Box::new(self)
    }
}

But no worries, it seems that bevy_serde_project primarily focuses on serializing and deserializing Components and Resources, rather than their internal fields.

If the approach is too tricky, I'm also exploring an alternative solution using serde_tagged

[mintlu8]

But it seems like I'm running into another problem with recursive dyn Traits. It looks like Serialize, Deserialize, and SerdeProject can't play nice together, and the generated __Ser is out of reach from the outside.

All Serialize + DeserializeOwned structs are SerdeProject so you should choose one of them. SerdeProject is meant to serialize non-serde structs.

Closing this since the issue is solved.