Rydantic derive

Procedural macros for Rydantic, a Rust library for data modeling, validation, JSON Schema and native Cap'n Proto.

Use the rydantic crate, which enables and re-exports #[derive(Model)] by default. This README describes the 0.7.0 stable release contract. Source metadata alone does not prove registry availability: verify both runtime and derive packages and the release record before using this exact pin:

[dependencies]
rydantic = "=0.7.0"

use rydantic::Model;

#[derive(Debug, Model)]
struct User {
    #[model(trim, min_length = 2)]
    name: String,
    #[model(ge = 18, le = 120)]
    age: u8,
}

let user = User::parse_json(r#"{"name":" Alice ","age":25}"#)?;
assert_eq!(user.name, "Alice");
# Ok::<(), rydantic::ValidationErrors>(())

See the API documentation and complete guide for borrowing, validators, model attributes, schemas and Cap'n Proto mappings.

With rydantic's capnp feature, #[rydantic::capnp_models] on an inline model module also infers the complete Cap'n Proto schema, invokes the installed official capnp compiler, and generates native Rust bindings automatically. Each struct and enum must explicitly derive rydantic::Model (or an imported alias). Consumers maintain Rust model definitions without a separate schema, generated source file, or build script. Breaking change in 0.7.0-beta.1: capnp_models no longer inserts Model derives; add the derive to models that previously relied on automatic insertion before upgrading. The schema is available through CapnpSchema and the model module's CAPNP_SCHEMA constant.

License: MIT.

Enable sqlite, postgres or mysql for #[derive(Model, SqlModel)]: the macro generates portable table metadata, validated SQLx row decoding for enabled drivers, and asynchronous CRUD with transactions. The pool type selects SQLite, PostgreSQL or MySQL while model definitions stay the same. migrate derives upgrades from the live catalog; rename_from preserves renamed columns and constant SQL defaults backfill required additions. Preview changes with migration_plan and explicitly opt in to column removal or storage conversions. Combine it with the axum feature to use one model for HTTP JSON validation and database persistence. See the complete guide for #[sql(...)] attributes, queries, and the Tokio HTTP server example.

rydantic-derive 0.7.0

Rydantic derive