Repository navigation
feat(jsonapi): opt-in strict resource type check on write - #8739
Merged
soyuka merged 3 commits intoOct 19, 2026
Merged
Conversation
A request body that is not a JSON:API document, has no data object, or has non-object attributes/relationships was accepted with 201 or crashed in array_merge() with a 500. Return 400 instead. A missing type is still accepted. Refs api-platform#8703
Add `jsonapi.strict_resource_type` (default false). When enabled, a request resource object without a string type is a 400, and on POST a type that is neither the operation shortName nor the type the serializer emits for the class is a 409 Conflict. Refs api-platform#8703
soyuka
marked this pull request as ready for review
October 19, 2026 13:03
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
1 participant
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.
Draft to see how this looks. Adds
api_platform.jsonapi.strict_resource_type(Laravel:api-platform.jsonapi.strict_resource_type, also usable per operation throughdenormalizationContext), defaultfalseso nothing changes. When enabled:typeis a 400typethat is neither the operation shortName nor the type the serializer emits for the class is a 409 Conflict (https://jsonapi.org/format/#crud-creating-responses-409), using a newApiPlatform\Metadata\Exception\ConflictExceptionAccepting the emitted type matters for classes declared as several resources, where the serializer always emits the first resource's shortName.
Includes the commit from #8736 (5.0), to rebase once it's merged up. A 6.0 default flip would go through a deprecation when the option is not set.