The struct mapper in zig-toml only reads keys that match struct fields; everything else is dropped without a warning (verified in the pinned dependency source).
A typo silently changes behavior instead of failing:
[observabilty] disables metrics with no signal.routing_kye falls back to default routing.
Strict mapping is hard to get from the pinned library. A realistic minimum: print the effective config at startup (partially exists via printConfigInfo) or validate top-level section and key names against the known set by walking the parsed TOML table before mapping.
The struct mapper in zig-toml only reads keys that match struct fields; everything else is dropped without a warning (verified in the pinned dependency source).
A typo silently changes behavior instead of failing:
[observabilty]disables metrics with no signal.routing_kyefalls back to default routing.Strict mapping is hard to get from the pinned library. A realistic minimum: print the effective config at startup (partially exists via
printConfigInfo) or validate top-level section and key names against the known set by walking the parsed TOML table before mapping.