Ignore container when deserializing

[steven-joruk]

Hi, I'd like to handle this kind of deserialization:

<root>
    <ignored>
        <item id="1"/>
        <item id="2"/>
    </ignored>
</root>

#[derive(YaDeserialize)]
#[yaserde(rename = "item")]
struct Item {
    id: String,
}

#[derive(YaDeserialize)]
#[yaserde(rename = "root")]
struct Root {
    /// Some yaserde attribute or custom deserializer to get rid of the `ignored` container.
    items: Vec<Item>,
}

Adding a custom deserializer for a newtype doesn't feel much better than just declaring the container type, and there doesn't seem to be an equivalent of serde's deserialize_with attribute.

Presuming there isn't a good way of handling this already, would you be interested in a PR to allow users to ignore containers like this?

Thanks.

[MarcAntoine-Arnaud]

Hello @steven-joruk

Humm yes you have to declare all levels.

#[derive(YaDeserialize)]
#[yaserde(rename = "item")]
struct Item {
    #[yaserde(attribute)]
    id: String,
}

#[derive(YaDeserialize)]
#[yaserde(rename = "ignored")]
struct Ignored {
    items: Vec<Item>,
}

#[derive(YaDeserialize)]
#[yaserde(rename = "root")]
struct Root {
    ignored: Ignored,
}

It can be very complex to allow to fill with sub-childs.
The invert example is: an XML like

<root id="0">
    <ignored id="5">
        <item id="1"/>
        <item id="2"/>
    </ignored>
    <other>
        <something id="3" />
    </other>
</root>

What can be expected in values from that ...
Which means Serialiser can't reproduce it !

[steven-joruk]

How about like adding an attribute to a field though, like this:

...
struct Root {
    #[yaserde(container = "ignored")]
    items: Vec<Item>,

    #[yaserde(container = "something")]
    somethings: Vec<Something>,
    ...

[MarcAntoine-Arnaud]

Hi again;
container will be rename in YaSerDe.
It can works.