WORKED CASE · SYNTHETIC TEST DATA

Check a nested configuration table in JSON

A TOML table header becomes an object boundary. Confirm nesting before replacing a configuration consumed by an application.

Input and settings

[server]
port = 8080
enabled = true

Run and interpret

Convert the sample and inspect the server object. The port is numeric and enabled is boolean, not string values.

Expected output

"server": {
"port": 8080
"enabled": true

Scope and possible misuse

Comments and source layout are lost. Unsafe integers are rejected. Date values can change representation through JavaScript Date, so test time-sensitive fields separately.

Unexpected result? Report a minimal example