YAML indentation and line width after JSON conversion

Use spaces, not tabs

YAML indentation must use spaces. Two spaces is a common default and works well for deeply nested configuration without creating very long leading whitespace.

Keep nested relationships visible

Every child level must be indented consistently beneath its parent. Sequence markers belong at the sequence level, and nested mapping keys line up beneath the sequence item.

Treat line width as a readability setting

Wrapping long scalars can change their presentation and sometimes their semantics. Review URLs, certificates, shell commands, and generated tokens before forcing a narrow line width.

A reliable step-by-step workflow

Treat YAML indentation and line width 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.

• Start with a representative input and keep an untouched copy so the transformation can be reviewed or repeated.
• Inspect the parsed structure, not only the rendered text; keys, scalar types, array order, and null values are what downstream software receives.
• Test the result in the real destination and record any parser, schema, encoding, or formatting assumptions in the project.

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:
  environment:
    LOG_LEVEL: info
    RETRIES: "3"

Limits and edge cases

The difficult cases in YAML indentation and line width 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.

• Start with a representative input and keep an untouched copy so the transformation can be reviewed or repeated.
• Inspect the parsed structure, not only the rendered text; keys, scalar types, array order, and null values are what downstream software receives.
• Test the result in the real destination and record any parser, schema, encoding, or formatting assumptions in the project.

Questions about this topic