Serde Debugability

[najaco]

For testing purposes, it would be nice to be able to serialize and deserialize packets in a human readable format. This adds an optional feature to derive the serialize and deserialize impls from the serde crate

In conjunction with netlink-packet-xfrm PR #8

[najaco]

Realistically, I think an effort could be made to get rid of NetlinkSerializable and NetlinkDeserializable, derive serde::Serialize and serde::Deserialize without it being a feature, and have your own netlink-serde encoder, similar to:

• https://github.com/serde-rs/json
• https://github.com/ron-rs/ron

Doing so would keep in line with traits defined by the serde crate. Such a task is outside the scope of this PR.

[cathay4t]

The serde is big crate to depend on. It is strange to me we need human friendly output for test purpose, why the {:?} is not good enough.

[najaco]

@cathay4t I can see your point on that, which is why I opted to make it a feature. We would find having the serde crate added on help us in recording messages in a human readable format, so that we can play them back in testing setups.

[najaco]

@cathay4t any update?

[cathay4t]

Sorry for the long wait. Please provide more detail on so that we can play them back in testing setups.

[cathay4t]

If you want to store data and apply it back. Try emit().