fix(serializer): correct supported types for elasticsearch item normalizer decorator#5769
Merged
Merged
Conversation
35b3643 to
51bdf2f
Compare
soyuka
reviewed
Aug 23, 2023
Contributor
|
Just discovered this issue as well! |
Member
|
Thanks! |
|
Since this fix I get following error: "Failed to denormalize attribute "origin" value for class "App\Document\Content": Expected argument of type "App\Document\Origin", "array" given at property path "origin".". Any idea how to fix this? Trace: POST data: |
Romaixn
pushed a commit
to Romaixn/core
that referenced
this pull request
Oct 3, 2023
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.
I have issue using DTO input (https://api-platform.com/docs/core/dto/#implementing-a-write-operation-with-an-input-different-from-the-resource). The state processor doesn't receive the input class as argument. There is a problem with the deserialization process.
This pull request fixes my issue.
With elasticsearch support enabled, the normalizer
api_platform.elasticsearch.normalizer.itemis registered, it decorates the default item normalizerapi_platform.serializer.normalizer.item.I guess that this
ApiPlatform\Elasticsearch\Serializer\ItemNormalizerclass intend to prevent calling the decorated service when usingelasticsearchformat.Unfortunately, recent patch on the
getSupportedTypesmethod break this.