DEBUGGING PLAYBOOK · REVIEWED 2026-10-08
A response changed type
A number can become a string or an empty list can become an object. Both documents still parse, but the consuming application may fail.
Sample input
{"count":1,"items":[]}Steps and checks
- Load the sample into JSON A. Set JSON B to {"count":"1","items":{}}.
- Differences appear automatically: /count changes from number to string, and /items from array to object.
- Replace B with {"items":[],"count":1}. The comparison now reports equality because object property order is ignored.
Reference result
A: {"count":1,"items":[]}
B: {"count":"1","items":{}}
/count: 1 → "1"
/items: [] → {}Avoid a misleading conclusion
Arrays are compared by index; reordering can produce multiple differences. Duplicate keys and unsafe numbers block comparison. A blocked comparison must not be interpreted as equality.
What to do next
Check each difference against the contract. Use Schema validation for required fields and value constraints; retain raw text when exact bytes matter.
Related case and technical reference · Report an error or missing edge case