qubit-config 0.8.0

Powerful type-safe configuration management with multi-value properties, variable substitution, and rich data type support
Documentation

qubit-config

CircleCI Coverage Status Crates.io Rust License 中文文档

A powerful, type-safe configuration management system for Rust, providing flexible configuration management with support for multiple data types, variable substitution, multi-value properties, and pluggable configuration sources (files, environment, and composites).

Features

  • Pure Generic API - Use get<T>() and set<T>() generic methods with full type inference support
  • Rich Data Types - Support for all primitive types, temporal types, strings, byte arrays, and more
  • Multi-Value Properties - Each configuration property can contain multiple values with list operations
  • Variable Substitution - Support for ${var_name} style variable substitution from config or environment
  • Type Safety - Compile-time type checking to prevent runtime type errors
  • Serialization Support - Full serde support for serialization and deserialization
  • Extensible - Trait-based design for easy custom type support
  • Configuration sources - ConfigSource trait with built-in loaders: TOML, YAML, Java-style .properties, .env files, process environment variables (with optional prefix / key normalization), and CompositeConfigSource to merge several sources in order (later entries override earlier ones for the same key); use Config::merge_from_source to populate a Config
  • Read-only API - ConfigReader trait for typed reads without mutation; implemented by Config and ConfigPrefixView, with string helpers (get_string, get_string_or, optional variants, lists) that respect variable substitution
  • Prefix views - Config::prefix_view returns a ConfigPrefixView scoped to a logical key prefix (relative keys map to prefix.key); nest with ConfigPrefixView::prefix_view
  • Zero-Cost Abstractions - Uses enums instead of trait objects to avoid dynamic dispatch overhead

Installation

Add this to your Cargo.toml:

[dependencies]
qubit-config = "0.2"

Quick Start

use qubit_config::Config;

fn main() -> Result<(), Box<dyn std::error::Error>> {
    let mut config = Config::new();

    // Set configuration values
    config.set("port", 8080)?;
    config.set("host", "localhost")?;
    config.set("debug", true)?;

    // Read configuration values (with type inference)
    let port: i32 = config.get("port")?;
    let host: String = config.get("host")?;
    let debug: bool = config.get("debug")?;

    // Use turbofish syntax
    let port = config.get::<i32>("port")?;

    // Use default values
    let timeout: u64 = config.get_or("timeout", 30);

    println!("Server running on {}:{}", host, port);
    Ok(())
}

Core Concepts

Config

The Config struct is the central configuration manager that stores and manages all configuration properties.

let mut config = Config::new();
config.set("database.host", "localhost")?;
config.set("database.port", 5432)?;

Property

Each configuration item is represented by a Property that contains:

  • Name (key)
  • Multi-value container
  • Optional description
  • Final flag (immutable after set)

MultiValues

A type-safe container that can hold multiple values of the same data type.

ConfigReader and ConfigPrefixView

ConfigReader is the read-only configuration surface. Functions or types that only need to read settings can take &impl ConfigReader (or &dyn ConfigReader) instead of &Config, and the same API works for a full Config or a scoped prefix view. Besides get / get_list, contains, contains_prefix, and iter_prefix, the trait provides default helpers such as get_string, get_string_or, get_string_list, get_optional_string, and list variants, all consistent with the owning config’s variable substitution settings.

ConfigPrefixView is a zero-copy borrow of a Config with a logical key prefix (distinctly named so other view kinds can be added later). Use Config::prefix_view to create it; keys you pass are resolved under that prefix (for example, prefix db and key host reads db.host). Use ConfigPrefixView::prefix_view to obtain a nested prefix view. iter_prefix and contains_prefix only see keys exposed relative to the view’s prefix.

use qubit_config::{Config, ConfigReader};

let mut config = Config::new();
config.set("db.host", "localhost")?;
config.set("db.port", 5432i32)?;

let db = config.prefix_view("db");
let host: String = db.get_string("host")?;
let port: i32 = db.get("port")?;

Configuration sources

Implementations of ConfigSource load external settings into a Config. Call merge_from_source (or load on the source with a &mut Config) to apply them.

Type Role
TomlConfigSource TOML files; nested tables are flattened to dot-separated keys
YamlConfigSource YAML files; nested mappings flattened similarly
PropertiesConfigSource Java .properties files
EnvFileConfigSource .env-style files
EnvConfigSource Process environment; optional prefix filtering and key normalization (e.g. APP_SERVER_HOSTserver.host)
CompositeConfigSource Chains multiple sources in order; later sources win on duplicate keys (subject to Property final semantics)
use qubit_config::{Config, source::{
    CompositeConfigSource, ConfigSource, EnvConfigSource, TomlConfigSource,
}};

let mut config = Config::new();
let mut composite = CompositeConfigSource::new();
composite
    .add(TomlConfigSource::from_file("config.toml"))
    .add(EnvConfigSource::with_prefix("APP_"));
config.merge_from_source(&composite)?;

Usage Examples

Basic Configuration

use qubit_config::Config;

let mut config = Config::new();

// Set various types
config.set("port", 8080)?;
config.set("host", "localhost")?;
config.set("debug", true)?;
config.set("timeout", 30.5)?;

// Get values with type inference
let port: i32 = config.get("port")?;
let host: String = config.get("host")?;
let debug: bool = config.get("debug")?;

Multi-Value Configuration

// Set multiple values
config.set("ports", vec![8080, 8081, 8082])?;

// Get all values
let ports: Vec<i32> = config.get_list("ports")?;

// Add values incrementally
config.set("server", "server1")?;
config.add("server", "server2")?;
config.add("server", "server3")?;

let servers: Vec<String> = config.get_list("server")?;

Variable Substitution

config.set("host", "localhost")?;
config.set("port", "8080")?;
config.set("url", "http://${host}:${port}/api")?;

// Variables are automatically substituted
let url = config.get_string("url")?;
// Result: "http://localhost:8080/api"

// Environment variables are also supported
std::env::set_var("APP_ENV", "production");
config.set("env", "${APP_ENV}")?;
let env = config.get_string("env")?;
// Result: "production"

Structured Configuration

#[derive(Debug)]
struct DatabaseConfig {
    host: String,
    port: i32,
    username: String,
    password: String,
}

let mut config = Config::new();
config.set("db.host", "localhost")?;
config.set("db.port", 5432)?;
config.set("db.username", "admin")?;
config.set("db.password", "secret")?;

let db_config = DatabaseConfig {
    host: config.get("db.host")?,
    port: config.get("db.port")?,
    username: config.get("db.username")?,
    password: config.get("db.password")?,
};

Configurable Objects

use qubit_config::{Configurable, Configured};

// Use the Configured base class
let mut configured = Configured::new();
configured.config_mut().set("port", 3000)?;

// Custom configurable object
struct Application {
    configured: Configured,
}

impl Application {
    fn new() -> Self {
        Self {
            configured: Configured::new(),
        }
    }

    fn config(&self) -> &Config {
        self.configured.config()
    }

    fn config_mut(&mut self) -> &mut Config {
        self.configured.config_mut()
    }
}

let mut app = Application::new();
app.config_mut().set("port", 3000)?;

Supported Data Types

Rust Type Description Example
bool Boolean value true, false
char Character 'a', '中'
i8, i16, i32, i64, i128 Signed integers 42, -100
u8, u16, u32, u64, u128 Unsigned integers 255, 1000
f32, f64 Floating point 3.14, 2.718
String String "hello", "世界"
Vec<u8> Byte array [1, 2, 3, 4]
chrono::NaiveDate Date 2025-01-01
chrono::NaiveTime Time 12:30:45
chrono::NaiveDateTime Date and time 2025-01-01 12:30:45
chrono::DateTime<Utc> Timestamped datetime 2025-01-01T12:30:45Z

Extending with Custom Types

To support custom types in the configuration system, you need to implement the necessary traits from qubit_value. The configuration system uses the MultiValues infrastructure for type-safe storage and retrieval.

Here's an example of how to work with custom types:

use qubit_config::Config;

// Define your custom type
#[derive(Debug, Clone, PartialEq)]
struct Port(u16);

// You can use the configuration system with types that can be converted to/from primitive types
impl Port {
    fn new(value: u16) -> Result<Self, String> {
        if value < 1024 {
            Err("Port must be >= 1024".to_string())
        } else {
            Ok(Port(value))
        }
    }

    fn value(&self) -> u16 {
        self.0
    }
}

// Usage with the configuration system
let mut config = Config::new();

// Store the port as a primitive type
config.set("port", 8080u16)?;

// Retrieve and wrap in custom type
let port_value: u16 = config.get("port")?;
let port = Port::new(port_value).map_err(|e| ConfigError::ConversionError(e))?;

// Or use get_or with validation
let port = Port::new(config.get_or("port", 8080u16))
    .map_err(|e| ConfigError::ConversionError(e))?;

For more advanced type conversions, you can implement the traits from qubit_value (MultiValuesFirstGetter, MultiValuesSetter, etc.). See the qubit_value documentation for details on implementing these traits for custom types.

API Design Philosophy

Why Pure Generic API?

We use a pure generic approach (only providing get<T>(), set<T>(), get_or<T>() core methods) instead of type-specific methods (like get_i32(), get_string(), etc.) because:

  1. Universal - Generic methods work with any type that implements the required traits, including custom types
  2. Concise - Avoids repetitive type-specific method definitions
  3. Maintainable - Adding new types only requires trait implementation, no modification to Config struct
  4. Idiomatic Rust - Leverages Rust's type system and type inference capabilities

Three Ways of Type Inference

// 1. Variable type annotation (recommended, most clear)
let port: i32 = config.get("port")?;

// 2. Turbofish syntax (use when needed)
let port = config.get::<i32>("port")?;

// 3. Context inference (most concise)
struct Server {
    port: i32,
}
let server = Server {
    port: config.get("port")?,  // Inferred from field type
};

Error Handling

The configuration system uses ConfigResult<T> for error handling:

pub enum ConfigError {
    PropertyNotFound(String),           // Property does not exist
    PropertyHasNoValue(String),         // Property has no value
    TypeMismatch { expected: DataType, actual: DataType }, // Type mismatch
    ConversionError(String),            // Type conversion failed
    IndexOutOfBounds { index: usize, len: usize }, // Index out of bounds
    SubstitutionError(String),          // Variable substitution failed
    SubstitutionDepthExceeded(usize),   // Variable substitution depth exceeded
    MergeError(String),                 // Configuration merge failed
    PropertyIsFinal(String),            // Property is final and cannot be overwritten
    IoError(std::io::Error),            // IO error
    ParseError(String),                 // Parse error
    Other(String),                      // Other errors
}

Performance Considerations

  • Zero-Cost Abstractions - Uses enums instead of trait objects to avoid dynamic dispatch overhead
  • Variable Substitution Optimization - Uses OnceLock to cache regex patterns, avoiding repeated compilation
  • Efficient Storage - Properties stored in HashMap with O(1) lookup time complexity
  • Shallow Copy Optimization - Cloning uses shallow copies when wrapped in Arc

Testing

Run the test suite:

cargo test

Run with code coverage:

./coverage.sh

Documentation

For detailed API documentation, visit docs.rs/qubit-config.

For internal design documentation (Chinese), see src/README.md.

Dependencies

  • qubit-common - Core utilities and data type definitions
  • qubit-value - Value handling framework
  • serde - Serialization framework
  • chrono - Date and time handling
  • regex - Regular expression support
  • toml - TOML parsing for TomlConfigSource
  • serde_yaml - YAML parsing for YamlConfigSource
  • dotenvy - .env file parsing for EnvFileConfigSource

Roadmap

  • Additional configuration loaders (e.g. JSON, XML)
  • Advanced merge / overlay policies beyond ordered CompositeConfigSource
  • Configuration watching and hot reload
  • Configuration validation framework
  • Configuration encryption support
  • Thread-safe wrapper type SyncConfig

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

Copyright (c) 2025 - 2026. Haixing Hu, Qubit Co. Ltd. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

See LICENSE for the full license text.

Author

Haixing Hu - Qubit Co. Ltd.


For more information about the Qubit Rust libraries, visit our GitHub organization.