Thisversion: Keep schema history out of your application model

Дата публикации: 05-10-2026 12:39:46

Persisted data often outlives the code that wrote it. As an application evolves, its stored fields and their meanings change too. I built thisversion to keep that history in versioned schema types, while letting application code use one current model.
The idea for this library came from my place of work, where managing backwards compatibility became increasingly burdensome as our types accumulated changes over the years. I cleaned up and documented the approach so it could be useful to other Rust projects too.
With thisversion, you define a type for each schema version and write conversions between versions. Derives connect the schema history to your current application type, so Rust checks the connection when the model changes.
use thisversion::{VersionBoundary, VersionFamily};
use thisversion::traits::{IntoModel, IntoSchema};
#[derive(VersionFamily)]
enum SettingsVersions {
V1(SettingsV1),
V2(SettingsV2),
V3(SettingsV3),
}
// Historical schemas each have their own shape.
struct SettingsV1 { /* older schema */ }
struct SettingsV2 { /* newer fields */ }
#[derive(VersionBoundary)]
#[thisversion(model = Settings)]
struct SettingsV3 { /* current persisted schema */ }
// Migrations connect each historical schema to the next.
impl From<SettingsV1> for SettingsV2 { /* ... */ }
impl From<SettingsV2> for SettingsV3 { /* ... */ }
#[derive(VersionBoundary)]
#[thisversion(model = Settings)]
struct SettingsV3 { /* current persisted schema */ }
// Application code uses a completely isolated type.
struct Settings { /* current application model */ }
// Decode any stored version, then migrate it into the current model.
let versions: SettingsVersions = decode_from_somewhere(...);
let settings: Settings = versions.into_model();
// Convert back to the latest schema for persistence.
let schema: SettingsVersions = settings.into_schema();
The crate is no_std by default. Optional Serde adapters are available, but the migration layer does not require Serde or prescribe a storage system or wire format.
Links: crates.io · documentation · repository and examples
I'd love to get this to 1.0, but need some adoption and feedback before I feel comfortable committing to a 1.0 release.
The name is an homage thiserror and this is my first ever publication to crates.io!
1 post - 1 participant
Read full topic

Схожие новости

#	Наименование новости	Тональность	Информативность	Дата публикации
1	Architecture review of a Hyper/Tower-based web framework (Toxi)	0	15.46	06-10-2026
2	I built a library for automatic callback encoding/decoding for Teloxide	0	8.24	05-10-2026
3	Strategies for dyn trait objects with optional behavior?	0	7.12	06-10-2026
4	Adya 0.1: black-box transactional isolation checker (Elle-style) with a workload runner	0	16.28	06-10-2026
5	Does my lockfree stack impl look correct?	0	6.06	05-10-2026
6	What's everyone working on this week (41/2026)?	0	20.34	06-10-2026
7	Are there wait-free priority queue crates?	0	16.09	05-10-2026
8	Nuthatch: a blockchain indexer in one static Rust binary (redb, content-addressed Parquet, DataFusion, DBSP)	0	8.24	04-10-2026
9	Why is f32/f64::sqrt not const?	0	22.72	06-10-2026
10	Trait object with associated types in field - requires generic param?	0	11.08	07-10-2026

Классификация: . Схожих патентов: 0. Схожих новостей: 10. Тональность: 0. Информативность: 7.06. Источник: users.rust-lang.org.