JSON ↔ YAML Converter

// HOW TO USE

1. 01Pick a direction — JSON → YAML or YAML → JSON.
2. 02Paste your source document, then click Convert.
3. 03Swap flips the direction and moves the output back to the input — handy for round-trip checks.

// WHEN TO USE

Use this when you need to translate a JSON config, fixture, or API response into YAML for a CI pipeline, Kubernetes manifest, or test framework config — or the reverse when a YAML document needs to become JSON for tooling that doesn't parse YAML. Use Swap for round-trip checks: convert JSON → YAML, then YAML → JSON, and compare against the original to confirm nothing is lost or type-coerced in the conversion.

// WHAT BUGS THIS FINDS

• Type coercion in YAML output

  YAML parsers treat unquoted 'yes', 'no', 'true', 'on' as booleans — a JSON string value 'yes' that survives conversion unquoted may be parsed as a boolean by the consumer. Convert and review the YAML output for unintended type changes.

• Numeric string becomes number

  A JSON value '01234' is a string; YAML may emit it as the integer 1234 without quotes — Convert and inspect the output to catch values that require explicit YAML string quoting.

• Round-trip data loss

  Some structures survive JSON → YAML → JSON with subtle differences (null vs empty string, key ordering). Swap and re-convert to confirm the round-trip is lossless before committing the YAML file.

• Indentation format mismatch

  A downstream YAML parser configured for 4-space indentation rejects 2-space output — Convert shows the exact indentation style so you can flag parser configuration mismatches early.

// QA USE CASES