Hacker News Reader

YAML is great for human-readable configuration, but many APIs and tools expect JSON.

I wrote this short guide to explain when YAML → JSON conversion is required, common pitfalls (indentation, duplicate keys, anchors), and how this shows up in real Kubernetes and API workflows.

Feedback welcome.

View on HN

Is there an actual guide? It seems you've mainly pasted something along the lines of a ChatGPT output to a Github Pages html.

Fair question.

The GitHub Pages article is intentionally minimal, but it’s not meant to be a generic LLM dump. The examples come from real issues I’ve hit while working with Kubernetes manifests and CI pipelines — especially duplicate keys, implicit type coercion, and indentation edge cases that silently break JSON conversion.

I’m actively expanding it with: - concrete Kubernetes + API payload examples - cases where YAML parses but produces invalid JSON - notes on tooling differences (yq, js-yaml, browser-based parsers)

The online converter exists mainly as a reference implementation that runs fully client-side and exposes these edge cases clearly: https://jsonviewertool.com/yaml-to-json

Happy to improve the guide based on feedback — appreciate the pushback.

Reply on news.ycombinator.com