WORKED CASE · SYNTHETIC TEST DATA

Preserve a nested application setting in TOML

A nested JSON object needs a TOML table representation; quoting the key also protects punctuation in configuration names.

Input and settings

{"server":{"port":8080}}

Run and interpret

Convert the sample and verify the inline table and equals signs. The port stays numeric rather than becoming quoted text.

Expected output

"server" = { "port" = 8080 }

Scope and possible misuse

TOML has no null value, so null is rejected. JSON warnings such as duplicate keys or unsafe numbers must be resolved before conversion.

Unexpected result? Report a minimal example