Repository navigation
Nested DTO not deserialized #5160
Unanswered
MichaelKubovic
asked this question in
Q&A
Replies: 4 comments
|
Would you be able to debug this a bit more? The denormalization of this is done here: It'd be interesting to know what it does when it encounters |
0 replies
|
We have no way to know how to denormalize those objects. You'd have to do this in your |
0 replies
|
@teohhanhui I have the same issue (array of strings instead of array of DTO's) and wrote comment in this issue api-platform/api-platform#1202 (comment) with some debug experience. Offtop: can you explain: all issues from |
0 replies
|
@MichaelKubovic @teohhanhui I found the solution, you have to configure DocumentationNormalizer like this: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
API Platform version(s) affected: 2.5.3
Description
Having a resource that uses DTO for input and that class contains property that contains array of DTOs of other class.
Generated documentation says that the property has type of array of strings.
Sending a request actually makes the data of the nested dto available as an associative array, although I'd expect it to be deserialized into an object.
How to reproduce
Possible Solution
Additional Context
All reactions