Guides
Each guide starts from an error message or a surprising result, shows the input that causes it, and links to the tool that checks it.
- error converting YAML to JSON
What the kubectl error means, how to read the part after the colon, and what a syntax check cannot catch.
- Mapping values are not allowed here
An unquoted colon or a misaligned key breaks a YAML mapping. Quote the value or fix the indentation.
- Found character that cannot start any token
A tab used as indentation, or a value that starts with @ or a backtick. Use spaces, or quote the value.
- Expected double-quoted property name in JSON
A trailing comma, a comment, a single quote, or an unquoted key. JSON allows none of them.
- YAML multiline strings: | and >
Literal and folded blocks, the - and + chomping indicators, and the JSON string each one produces.
- Redefining a table in TOML
A repeated key, a repeated [table], or an inline table extended later. How to merge them, and when to use [[array]].
- Why yes is not true
YAML 1.2 core schema keeps yes, no, on, and off as strings. true and false are the booleans.
- How TOML dates become strings
TOML dates and times become strings. Offset datetimes keep their offset, and local dates stay calendar dates.
- Why comments disappear
JSON has no comments. Converting YAML or TOML drops them, and a hash inside a quoted string is kept.
- Why .env values stay strings
.env values stay strings. 8080 and false are not converted, and $ references are rejected instead of expanded.