Should I use Serde for `google-apis-rs` ? about serde HOT 6 CLOSED

Actually there is no choice, and I am using it already !
It was already a great learning experience, as I was forced to dig into macros and compiler plugins a little more.
Without it, I would be totally lost, thanks for making serde in the first place !

from serde.

Happy to help! Let me know if you run into any problems. Just to let you know I've been iterating a lot on it recently which changes some of the Apis, which I hope to have a new release out this weekend.

from serde.

Great to hear ! Actually I have found two issues already - I will just list them here so we can figure out what to do with them. It's totally possible that I just don't know how to use serde correctly :).

Problem 1 (minor)

When sending requests to the server as json, these may be partial, thus only a few fields are actually set. Optional fields are declared with Option<_> properties that are None. Currently they end up as "field"=Null in json, which is valid, but wastes space

Possible solution: option to omit 'name=null' during serialize

Problem 2 (critical)

If I deserialize server replies to a respective struct, the said deserialization will fail if the server responds with all known AND added fields. There should be a way to say 'ignore extra fields' when deserializing. Otherwise my API will be out-of-date quickly thanks to it's growing inability to deserialize server responses.

Possible solution: option to ignore fields we don't have in target struct

Thanks for your input.

from serde.

I filed #43 and #44 for these issues :)

from serde.

Awesome :) ! Thanks !

from serde.

By the way: You can see how a relatively uninitiated user (me) uses serde on youtube.

from serde.