Config¶
Config loads one file or a directory of JSON or YAML files, deep-merges them,
and optionally resolves references.
Example YAML:
service:
host: localhost
port: 8080
service_url: "https://${service.host}:${service.port}"
profiles:
base:
debug: true
timeout: 30
production:
__extends__: "@{profiles.base}"
debug: false
Usage:
from rn_forge.commons import Config
cfg = Config("config")
url = cfg.get("service_url")
production = cfg.get("production")
Reference forms:
${path}scalar interpolation@{path}dict splice#{path}list splice__extends__dict inheritance
Validating a document against a schema¶
Config merges and resolves; it does not say whether the result is well-formed.
When a hand-authored document has a fixed shape — a tool's config.toml, a
manifest — validate it with a StrictModel from the pydantic extra:
import tomllib
from rn_forge.commons.lang.models import StrictModel
class Repository(StrictModel):
name: str
archetype: str = "python-tool"
class ProjectConfig(StrictModel):
schema_version: int
repository: Repository
with open("config.toml", "rb") as handle:
config = ProjectConfig.parse(tomllib.load(handle), source="config.toml")
A StrictModel is strict (a string is never coerced to an integer), frozen, and
rejects any key it does not declare. A failure raises ModelValidationError, an
AppException whose message lists every failing key by dotted path — a missing
key, a wrong type and a misspelled key are reported together, not one per run.
errors holds the same failures as FieldError records. parse_model gives
the same reporting for a BaseModel that does not subclass StrictModel.
Choose it over DataclassMixin.from_dict when the author of the document needs
every mistake at once, or when the schema needs pydantic's validators. The extra
is opt-in, and rn_forge.commons never imports it, so a program that does not
use it pays nothing at import time.