qubit-config
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>()andset<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 -
ConfigSourcetrait with built-in loaders: TOML, YAML, Java-style.properties,.envfiles, process environment variables (with optional prefix / key normalization), andCompositeConfigSourceto merge several sources in order (later entries override earlier ones for the same key); useConfig::merge_from_sourceto populate aConfig - ✅ Read-only API -
ConfigReadertrait for typed reads without mutation; implemented byConfigandConfigPrefixView, with string helpers (get_string,get_string_or, optional variants, lists) that respect variable substitution - ✅ Prefix views -
Config::prefix_viewreturns aConfigPrefixViewscoped to a logical key prefix (relative keys map toprefix.key); nest withConfigPrefixView::prefix_view - ✅ Zero-Cost Abstractions - Uses enums instead of trait objects to avoid dynamic dispatch overhead
Installation
Add this to your Cargo.toml:
[]
= "0.2"
Quick Start
use Config;
Core Concepts
Config
The Config struct is the central configuration manager that stores and manages all configuration properties.
let mut config = new;
config.set?;
config.set?;
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. It also provides resolve_key, which converts a key in the current reader scope into a root-relative key path.
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 ;
let mut config = new;
config.set?;
config.set?;
let db = config.prefix_view;
let host: String = db.get_string?;
let port: i32 = db.get?;
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_HOST → server.host) |
CompositeConfigSource |
Chains multiple sources in order; later sources win on duplicate keys (subject to Property final semantics) |
use ;
let mut config = new;
let mut composite = new;
composite
.add
.add;
config.merge_from_source?;
Usage Examples
Basic Configuration
use Config;
let mut config = new;
// Set various types
config.set?;
config.set?;
config.set?;
config.set?;
// Get values with type inference
let port: i32 = config.get?;
let host: String = config.get?;
let debug: bool = config.get?;
Multi-Value Configuration
// Set multiple values
config.set?;
// Get all values
let ports: = config.get_list?;
// Add values incrementally
config.set?;
config.add?;
config.add?;
let servers: = config.get_list?;
Variable Substitution
config.set?;
config.set?;
config.set?;
// Variables are automatically substituted
let url = config.get_string?;
// Result: "http://localhost:8080/api"
// Environment variables are also supported
set_var;
config.set?;
let env = config.get_string?;
// Result: "production"
Structured Configuration
let mut config = new;
config.set?;
config.set?;
config.set?;
config.set?;
let db_config = DatabaseConfig ;
Configurable Objects
use ;
// Use the Configured base class
let mut configured = new;
configured.config_mut.set?;
// Custom configurable object
let mut app = new;
app.config_mut.set?;
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 Config;
// Define your custom type
;
// You can use the configuration system with types that can be converted to/from primitive types
// Usage with the configuration system
let mut config = new;
// Store the port as a primitive type
config.set?;
// Retrieve and wrap in custom type
let port_value: u16 = config.get?;
let port = new.map_err?;
// Or use get_or with validation
let port = new
.map_err?;
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:
- Universal - Generic methods work with any type that implements the required traits, including custom types
- Concise - Avoids repetitive type-specific method definitions
- Maintainable - Adding new types only requires trait implementation, no modification to Config struct
- 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?;
// 2. Turbofish syntax (use when needed)
let port = config.?;
// 3. Context inference (most concise)
let server = Server ;
Error Handling
The configuration system uses ConfigResult<T> for error handling:
Performance Considerations
- Zero-Cost Abstractions - Uses enums instead of trait objects to avoid dynamic dispatch overhead
- Variable Substitution Optimization - Uses
OnceLockto cache regex patterns, avoiding repeated compilation - Efficient Storage - Properties stored in
HashMapwith O(1) lookup time complexity - Shallow Copy Optimization - Cloning uses shallow copies when wrapped in
Arc
Testing
Run the test suite:
Run with code coverage:
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 definitionsqubit-value- Value handling frameworkserde- Serialization frameworkchrono- Date and time handlingregex- Regular expression supporttoml- TOML parsing forTomlConfigSourceserde_yaml- YAML parsing forYamlConfigSourcedotenvy-.envfile parsing forEnvFileConfigSource
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.