Redundant data sub-structure in additional-data APIs #365
Description
Describe the bug
The response of the following two API endpoints return redundant data -> data structure:
- PATCH
/api/v2/partitionings/{{partitioning_id}}/additional-data - GET
/api/v2/partitionings/{{partitioning_id}/additional-data
We probably want only 1 data level.
To Reproduce
Just call any of these two API endpoints and check the response.
Expected behavior
Only 1 nesting level.
Screenshots
The response is as follows:
{
"data": {
"data": {
"additionalData1": {
"value": "firstItem",
"author": "apiTest1ShotAD"
},
"additionalData2": {
"value": "secondItem",
"author": "apiTest1ShotAD"
},
"additionalData3": {
"value": "thirdItem",
"author": "apiTest1ShotAD"
}
}
},
"requestId": "a11cb0dc-f48b-4189-9078-44b3ee214b19"
}
Metadata
Metadata
Assignees
Labels
Type
Projects
Status