OpenAPI ↔ Rust. This is one compiler in a suite, all focussed on the same task: Compiler Driven Development (CDD).
Each compiler is written in its target language, is whitespace and comment sensitive, and has both an SDK and CLI.
The CLI—at a minimum—has:
cdd-rust --helpcdd-rust --versioncdd-rust from_openapi -i spec.jsoncdd-rust to_openapi -f path/to/codecdd-rust to_docs_json --no-imports --no-wrapping -i spec.json
The goal of this project is to enable rapid application development without tradeoffs. Tradeoffs of Protocol Buffers / Thrift etc. are an untouchable "generated" directory and package, compile-time and/or runtime overhead. Tradeoffs of Java or JavaScript for everything are: overhead in hardware access, offline mode, ML inefficiency, and more. And neither of these alternative approaches are truly integrated into your target system, test frameworks, and bigger abstractions you build in your app. Tradeoffs in CDD are code duplication (but CDD handles the synchronisation for you).
The cdd-rust compiler leverages a unified architecture to support various facets of API and code lifecycle management.
- Compilation:
- OpenAPI →
Rust: Generate idiomatic native models, network routes, client SDKs, database schemas, and boilerplate directly from OpenAPI (.json/.yaml) specifications. Rust→ OpenAPI: Statically parse existingRustsource code and emit compliant OpenAPI specifications.
- OpenAPI →
- AST-Driven & Safe: Employs static analysis (Abstract Syntax Trees via
syn) instead of unsafe dynamic execution or reflection, allowing it to safely parse and emit code even for incomplete or un-compilable project states. - Seamless Sync: Keep your docs, tests, database, clients, and routing in perfect harmony. Update your code, and generate the docs; or update the docs, and generate the code.
Prerequisites: Requires the Rust toolchain (Rust 1.70+ recommended).
You can install cdd-rust CLI globally using Cargo:
cargo install cdd-cliOr build from source:
git clone https://github.com/offscale/cdd-rust.git
cd cdd-rust
cargo build --releaseGenerate an Actix-Web server scaffolding from an OpenAPI specification:
cdd-rust from_openapi to_server -i spec.yaml -o src/apiGenerate an OpenAPI specification from existing Actix-Web routing code:
cdd-rust to_openapi -f src/api -o new_spec.yamlGenerate a fully-typed offline CLI tool based on your OpenAPI specification:
cdd-rust from_openapi to_sdk_cli -i spec.yaml -o src/cliuse cdd_core::openapi::parse::parse_openapi_spec;
use cdd_core::classes::emit::generate_dtos;
use std::fs;
fn main() -> Result<(), Box<dyn std::error::Error>> {
let spec = fs::read_to_string("spec.yaml")?;
let models = parse_openapi_spec(&spec)?;
// Generate idiomatic Rust structs from the OpenAPI Components/Schemas
let rust_code = generate_dtos(&models);
fs::write("models.rs", rust_code)?;
Ok(())
}cdd-rust leverages syn and quote for robust, declarative parsing and emitting of Rust Abstract Syntax Trees. This provides extreme resilience against syntax errors in incomplete files. The intermediate representation tightly mirrors the OpenAPI 3.2.0 spec, permitting a lossless translation layer between code and definitions. We've selected Actix-Web as the server target, Diesel for the ORM layer, and Reqwest for the client implementation, as they represent the dominant paradigms in the Rust ecosystem. Unlike other cdd-* tools, the Rust tool relies on macros and attributes to map tightly between OpenAPI parameters and Actix extractors natively.
Compiling this project to WebAssembly (WASM) is currently not possible natively due to deep asynchronous networking requirements (Tokio/mio) needed for server generation and testing workflows. See WASM.md for full context.
(The boxes below reflect the features supported by this specific cdd-rust implementation)
| Concept | Parse (From) | Emit (To) |
|---|---|---|
| OpenAPI (JSON/YAML) | ✅ | ✅ |
Rust Models / Structs / Types |
✅ | ✅ |
Rust Server Routes / Endpoints |
✅ | ✅ |
Rust API Clients / SDKs |
✅ | ✅ |
Rust ORM / DB Schemas |
✅ | ✅ |
Rust CLI Argument Parsers |
✅ | ✅ |
Rust Docstrings / Comments |
✅ | ✅ |
Licensed under either of
- Apache License, Version 2.0 (LICENSE-APACHE or https://www.apache.org/licenses/LICENSE-2.0)
- MIT license (LICENSE-MIT or https://opensource.org/licenses/MIT)
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.