YAML Validator

It checks indentation consistency (must be multiples of 2 spaces), detects unclosed quotes in values, catches bare boolean/numeric values that may need quoting, and flags indentation jumps that are too large between parent and child.

Yes. The validator processes all lines and can handle multi-document YAML separated by --- markers. Each document is checked independently for common formatting issues.

YAML is a human-readable data format that uses indentation instead of brackets. It supports comments, anchors, aliases, and multi-line strings. JSON is more compact and stricter. YAML is commonly used for configuration files (Docker, Kubernetes, Ansible, CI/CD pipelines).

YAML uses indentation to define structure. All items in the same block must use consistent indentation (spaces only — tabs are not allowed). A single space out of place can break the entire document. Common errors include mixing tabs and spaces or inconsistent nesting levels.

Yes. YAML is a superset of JSON — any valid JSON is also valid YAML. YAML adds additional features like comments, anchors for reusing data, and more readable multi-line strings. Most tools that accept YAML also accept JSON.

The Norway problem (unquoted 'no', 'yes', 'true', 'false' are parsed as booleans), the ':' followed by space starts a mapping, indentation must use spaces not tabs, and multi-line strings can behave unexpectedly without proper indicators (| or >).

No - this is a syntax and style checker, not a full YAML parser. It catches common formatting errors but doesn't parse anchors, aliases, or complex data types. For full validation, consider using a dedicated YAML library.