Formats¶
e-serde speaks five config formats through five pinned engines. Each page states the spec implemented, the engine behind it — exact version, enforced against the lockfiles by the test-suite — and the capabilities that can be relied on.
| Format | Spec | Engine | Version |
|---|---|---|---|
| JSON | RFC 8259 | msgspec.json |
0.21 |
| JSONC | Deno jsonc: JSON + comments + trailing commas | jsonc-parser |
0.33 |
| YAML | YAML 1.2 core schema, plus the 1.1 merge key | saphyr |
0.0.12 |
| TOML | TOML v1.1 | toml (toml-rs) |
1.1 |
| INI | de-facto INI: sections of string key/value, no interpolation | rust-ini |
0.21 |
| CSV | RFC 4180: headered records as list[dict], polars-style per-column type inference |
csv |
1.4 |
| TSV | RFC 4180 dialect: tab-delimited | csv |
1.4 |
The capability contract lives in code — eserde.STANDARDS — and every claim is executed
against the live codecs by test_standards.py. The pages below mirror that contract.