Why JSON to YAML Conversion Changes Values
Debug JSON and YAML conversion bugs caused by type coercion, comments, anchors, large numbers, nulls and schema differences.
Quick Answer
JSON and YAML do not preserve every concept in both directions. YAML can contain comments, anchors, aliases and implicit scalar types. JSON has stricter syntax and no comments. Conversion can change strings into booleans, drop comments, expand aliases or alter large numbers if the converter parses through JavaScript numbers.
Example Scenario
A team converts a YAML deployment file to JSON for a generated client. The value on was meant to be a string flag, but the converter treated it as a boolean-like scalar. A large numeric account id also lost precision after moving through JSON parsing.
Step-by-Step Explanation
- Validate the source format before converting.
- Identify values that must stay strings, especially ids and feature flags.
- Check booleans, nulls, timestamps and large numbers after conversion.
- Expect comments, anchors and aliases to be lost or expanded.
- Run the converted output through the destination schema validator.
Preserve Meaning, Not Just Syntax
A successful conversion only proves that one parser produced output. It does not prove that the receiving application interprets the same values. Compare the parsed structures, then compare the application behavior that depends on those fields.
When the value is an identifier, version, zip code, account number or feature flag, quote it deliberately if the destination accepts strings. Treat comments and anchors as source-authoring conveniences, not runtime data that will survive every conversion path.
Prevention Checklist
- Keep generated JSON and source YAML in separate ownership paths.
- Quote string-like values that look like booleans, dates or numbers.
- Use schema validation after conversion, not only parser validation before conversion.
- Review diffs at the data-structure level when changing converters.
Common Mistakes
- Assuming YAML comments survive JSON conversion.
- Parsing account ids or snowflake ids as JavaScript numbers.
- Ignoring YAML anchors and merge keys.
- Comparing pretty-printed output instead of parsed values.
FAQ
Can JSON represent YAML comments?
No. JSON has no comment syntax, so comments must live outside the converted data.
Why did a number change?
Large numbers can lose precision when they pass through JavaScript number parsing.
Should ids be strings?
Large identifiers are often safer as strings when exact preservation matters.