YAML Validator/Formatter

// HOW TO USE

1. 01Paste a YAML document — try the sample for a Cypress CI workflow.
2. 02Validate & Format checks syntax and pretty-prints. Errors include line and column where parsing failed.
3. 03Convert to JSON round-trips the parsed document back out as JSON for tooling that doesn't speak YAML natively.

// WHEN TO USE

Use this when authoring or reviewing CI/CD pipeline configs (GitHub Actions, GitLab CI, CircleCI), test framework configs (Playwright, Cypress, Jest), Kubernetes manifests, or Docker Compose files. YAML's indentation-sensitive syntax makes copy-paste errors invisible to the eye — Validate surfaces the exact line and column of a parse failure before the pipeline runs. Use Convert to JSON to feed a YAML config into a tool or script that only accepts JSON.

// WHAT BUGS THIS FINDS

• Indentation-caused parse errors

  A list item indented by 3 spaces instead of 2 silently breaks the YAML structure — Validate shows the exact line and column, far faster than reading a cryptic CI error.

• Boolean/string coercion surprises

  Unquoted values like 'yes', 'no', 'true', 'on' are parsed as booleans in YAML 1.1 — Convert to JSON reveals what the parser actually produced so you can add quotes where needed.

• Duplicate key silently overwriting

  A second occurrence of the same key in a mapping overwrites the first without error in some parsers — Format normalises the document so duplicates are visually obvious.

• Tab character in indentation

  YAML forbids tab characters for indentation; a tab from copy-paste causes a parser error that's invisible in many editors — Validate catches it immediately.

// QA USE CASES