Expand description
TOML structured processor.
Parses TOML input, walks the value tree, replaces matched field values, and serializes back to TOML preserving structure.
§Key Paths
Nested keys use the same dot-separated convention as the JSON processor:
database.password, server.credentials.token.
Array elements are traversed transparently — a rule for servers.host
matches the host field inside every table in the servers array.
§Non-String Scalars
When a FieldRule matches an integer, float, boolean, or datetime value,
that value is converted to a string replacement. This changes the TOML
type for that key but keeps the file syntactically valid. Use specific
field rules (e.g. "database.password") rather than "*" if you want
to avoid replacing non-sensitive numeric values.
Structs§
- Toml
Processor - Structured processor for TOML configuration files.