---
title: "Comment by Arnold Holm on \"JSON Formatting Is Not Validation: A Practical Debugging Checklist\" | Hashnode"
description: "For an order-message boundary, I would keep valid JSON with volume: 0 as a negative fixture beside a correctly typed, permitted quantity. Also keep a missing qu"
url: "https://hashnode.com/posts/json-formatting-is-not-validation-a-practical-debugging-checklist/6ac35306b7fe132762572bd1/comment/6ac49c8dcc9b576032a1e6ce"
---

[Discussion](https://hashnode.com/posts/json-formatting-is-not-validation-a-practical-debugging-checklist/6ac35306b7fe132762572bd1)

Comment [JSON Formatting Is Not Validation: A Practical Debugging Checklist](https://hashnode.com/posts/json-formatting-is-not-validation-a-practical-debugging-checklist/6ac35306b7fe132762572bd1)

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 6](https://hashnode.com/posts/json-formatting-is-not-validation-a-practical-debugging-checklist/6ac35306b7fe132762572bd1/comment/6ac49c8dcc9b576032a1e6ce)

For an order-message boundary, I would keep valid JSON with volume: 0 as a negative fixture beside a correctly typed, permitted quantity. Also keep a missing quantity separate from null: parser success and a successful HTTP response must not stand in for an accepted order state. Return the field-specific failure before any order submission, so a transport retry cannot hide a validation failure.
