DEBUGGING PLAYBOOK · REVIEWED 2026-10-08

A configuration code loses leading zeroes

A configuration value may look numeric while representing a string. A conversion is useful only if the receiving application reads the intended types.

Sample input

{"code":"0012","enabled":false,"items":["yes","no"]}

Steps and checks

  1. Load the sample and convert to YAML. Compare with the reference output.
  2. code must remain the string "0012", enabled the boolean false, and both items strings.
  3. Load the result using the YAML parser and version deployed in your application. Check types and leading zeroes, not just visual similarity.

Reference result

code: '0012'
enabled: false
items:
  - 'yes'
  - 'no'

Avoid a misleading conclusion

Quotes are deliberate. Removing them can change interpretation in other YAML parsers. Duplicate keys and numeric risks stop conversion. Formatting and signatures are not preserved.

What to do next

Test the configuration in the receiving application and retain the source for review. Successful format conversion does not prove that the application accepts the configuration.

Related case and technical reference · Report an error or missing edge case

Continue this workflow

Check strings and booleans when converting JSON to YAML →

About this tool

Converts JSON values to YAML after checking syntax, duplicate keys and numeric precision risks. Conversion stops when detected issues could discard or round values.

How to use

Paste JSON or send it from the JSON formatter, then convert. For example, {"enabled":true} becomes enabled: true. Use Inspect to return problematic input to the formatter.

Tips & Notes

Converting changes serialization and does not preserve exact bytes. Use strings for large identifiers and do not transform a signed payload before verifying its signature.