Repository navigation
fix(contract): a response without content is not a response without a body - #13
Merged
Merged
Conversation
… body Only 204 / 205 / 304 and HEAD never carry a body (RFC 9110). A response without documented content is "not described": its body is accepted and not checked, with a note (Playwright annotation / pytest warning) and MISSING_RESPONSE_SCHEMA in coverage-gaps.json. Found on Toolshop: 15 correct 422 rejections of POST /products and GET /product-specs/names failed as unexpected-body. Same rule in validator.ts and contract.py. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only 204 / 205 / 304 and HEAD never carry a body (RFC 9110). A response without documented
contentis "not described": its body is accepted and not checked, with a note andMISSING_RESPONSE_SCHEMA. Found on Toolshop: 15 correct 422 rejections ofPOST /productsandGET /product-specs/namesfailed as unexpected-body. Same rule in validator.ts and contract.py; the shared case table (now 25 cases) passes in both.