Lists in JSON responses do not have root level keys
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Solum |
Triaged
|
Low
|
Amit |
Bug Description
For Example:
GET /assemblies
[
{
"status": "READY",
"plan_uri": "http://
"user_id": "04320243e43945
"name": "test",
"tags": null,
"uri": "http://
"uuid": "a1acbbff-
"type": "assembly",
},
{
"status": "READY",
"plan_uri": "http://
"user_id": "04320243e43945
"name": "test_pass",
"tags": null,
"uri": "http://
"uuid": "25b46dff-
"type": "assembly",
}
]
However, the list should have a key associated with it as show below. This will be necessary when pagination is implemented and other attributes such as "next" and "previous" are added.
{
"assemblies": [
{
"name": "test",
"tags": null,
"uri": "http://
"uuid": "a1acbbff-
"type": "assembly",
},
{
"name": "test_pass",
"tags": null,
"uri": "http://
"uuid": "25b46dff-
"type": "assembly",
}
]
}
tags: | added: low-hanging-fruit |
Changed in solum: | |
assignee: | nobody → Deepak Bhaskaran (dbhaskaran) |
Changed in solum: | |
assignee: | nobody → Amit (mail2amit19) |
Deepak Bhaskaran, please re-claim this bug if you plan to work on it.