Expand description
§Serde version
Versioning support for serde.
When software are developped and used at the same time the data formats may change from one version to another and persisting data may be produced by a specific version and loaded by another version.
Serde version provide a versioning feature for serde for the main use cases.
See the guide here.
Note 1: Requires the specialization feature.
Note 2: Use the derive feature to generate the DeserializeVersioned implementation
§Goals of Serde version
We aim at solving the case were a type or a set of types in a deserializer’s data needs to be upgraded to their latest format. This is the case when a mandatory property was added or removed, or an existing property changed.
§Non goals
This is based on types that can be upgraded individually. Types that needs to be upgraded together is way more complex to handle and usually relies on domain specific deserializer.
So, these data format should be handle with specific Deserialize traits implementations.
Modules§
Macros§
- Create an enum that maps an entry to a
VersionGroupURI<T> - Instantiate a
VersionGroupResolverwith specified version groups - Generate a static field initialized with specified version groups
- Instantiate a
VersionMapwith specified type’s version - Generates a static field initialized with specified
VersionMap.
Structs§
- Error used when a provided version number is not handled by current code
- An uri identifying a version group.
- A set of version group uris.
- A wrapper around a deserialize to support the deserialization.
Enums§
- Error wrapper to add the version number related errors
Traits§
- Implement this trait to provide a method to aggregate version maps
- Trait for versioning support during deserialization
- Find the
VersionMapassociated to aVersionGroupURI - Maps the version number for each deserialization type name