Configuration guides

Check exact integers and date text in a TOML to YAML export

·

When moving TOML data to YAML, check values whose types matter to the destination. The example contains an array of tables, a 64-bit integer and a timestamp with an offset and fractional seconds.

TOML to YAML

Check both route entries in the YAML sequence

Load the example and choose Convert to YAML. The service mapping has a route sequence containing the name static first and assets second. The ports sequence contains the integers 80 and 443.

The service label is quoted as "007". Inspect the health mapping for the path "/ready" and the boolean false.

TOML arrays of tablesYAML 1.2.2 core schema and tags

Compare the serial and timestamp with the source

The serial converts from 9_223_372_036_854_775_807 to the integer 9223372036854775807. The separator underscores are display syntax in TOML. Check that the last digits are 5807 before importing the output.

The release value becomes the string "2025-06-30T09:30:00.123456+05:30". The exported text preserves the offset and fractional digits. If the receiving application needs a timestamp object, configure how it reads that value.

TOML integer syntax and sizingTOML offset date-time and fractional precisionYAML 1.2.2 core schema and tags

Open the download in the receiving YAML reader

Download converted.yaml, then check the route order and the type of label in the reader your application will use. Use an integer-aware reader for values outside the range of exact JavaScript numbers.

Save the original TOML alongside the export when you need its comments and formatting for review.

YAML 1.2.2 core schema and tags

Common questions

How do empty TOML arrays and tables appear?

An empty array becomes [] and an empty table becomes {}. An empty string is quoted as "".

Can a whole-number float stay a float?

A value such as 1.0 is exported as a YAML float so an integer-aware reader can distinguish it from the TOML integer 1.

Sources

Put it into practice.

Related guides