Fix invalid JSON before converting it to YAML

Common invalid JSON patterns

JSON requires double-quoted keys and strings. It does not permit comments, trailing commas, undefined, NaN, or JavaScript object syntax.

{
  "name": "demo",
  "enabled": true,
}

Read the parser position

The line and column usually point near the unexpected token. Check the preceding comma, quote, bracket, or brace because the real cause can be immediately before the reported position.

Validate before trusting the YAML

Do not silently repair unknown source data. Correct the JSON deliberately, validate it, then convert and compare the resulting structure.

A reliable step-by-step workflow

Treat invalid JSON before YAML conversion as a data transformation with an explicit input, expected structure, and destination. Work on a copy, validate before changing representation, and isolate the smallest useful sample. This separates syntax failures from data-model or application failures.

Run one change at a time and repeat the same validation after each change. For automated pipelines, fail the job on a parser error instead of publishing a partial or guessed result. Keep the original input beside the generated artifact when traceability matters.

• Fix the first reported error before later ones; one missing quote can create many secondary messages.
• Reduce a large document to the smallest failing fragment while preserving the nesting around the error.
• After syntax succeeds, verify required keys, value types, ranges, and application-specific rules.

Worked example and verification

The compact sample below is intentionally small enough to inspect by eye. Use the same pattern with a real document: confirm every key, scalar type, list order, and nested boundary before accepting the output.

A successful conversion or minification only proves that the source could be parsed. Compare the parsed value before and after the operation, then load the result with the same library or platform that will consume it in production.

{
  "service": "api",
  "ports": [8080, 8443]
}

Limits and edge cases

The difficult cases in invalid JSON before YAML conversion usually come from differences between syntax validity and application validity. A parser can accept data that is still incomplete, ambiguous, too large, or incompatible with a destination schema.

Never repair or normalize an unfamiliar document blindly. Duplicate keys, implicit types, aliases, precision limits, Unicode, line endings, and very large inputs deserve an explicit policy. When the destination has stricter rules, those rules win.

Production checklist

Before release, test a normal document, an empty value, deeply nested data, non-ASCII text, and a deliberately malformed example. Record the tool or library version if another system must reproduce the exact output.

Make validation part of continuous integration when the data affects builds, deployments, APIs, or configuration. Review diffs, keep a rollback copy, and monitor the first consumer after deployment rather than assuming a syntactically valid file is operationally correct.

• Fix the first reported error before later ones; one missing quote can create many secondary messages.
• Reduce a large document to the smallest failing fragment while preserving the nesting around the error.
• After syntax succeeds, verify required keys, value types, ranges, and application-specific rules.

Questions about this topic