docs: document body validation with custom content type parsers#6556
Merged
docs: document body validation with custom content type parsers#6556
Conversation
When using the body schema `content` property to validate per content type, custom content type parsers require their content type to be listed in the schema for validation to apply. Without it, data is parsed but not validated. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
jsumners
reviewed
Mar 5, 2026
Co-authored-by: James Sumners <321201+jsumners@users.noreply.github.com> Signed-off-by: Matteo Collina <matteo.collina@gmail.com>
jsumners
approved these changes
Mar 6, 2026
Eomm
approved these changes
Mar 7, 2026
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
3 participants
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.
Summary
contentproperty for per-content-type validation, custom content type parsers need their content type listed in the schema or the incoming data will be parsed but not validatedapplication/yamlexample showing the correct setupTest plan
Validation-and-Serialization.mdandContentTypeParser.md#body-content-type-validationresolves correctly🤖 Generated with Claude Code