-
Sub-task
-
Resolution: Done
-
Major
-
None
-
5
-
False
-
None
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
-
-
API CCS Sprint 37 (3Scale), API CCS Sprint 38 (3Scale), API CCS Sprint 39 (3Scale), API CCS Sprint 40 (3Scale), API CCS Sprint 42 (3Scale), API CCS Sprint 43 (3Scale), API CCS Sprint 44 (3Scale) 2
XML responses from the CMS API endpoint are default now and contain the agreed data, but JSON responses are incomplete or make not much sense. The JSON responses should include the same data as the XML ones.
List of affected endpoints
GET /admin/api/cms/sections/:section_id/files.json GET /admin/api/cms/sections.json GET /admin/api/cms/sections/:id.json GET /admin/api/cms/files.json GET /admin/api/cms/files/:id.json GET /admin/api/cms/templates.json GET /admin/api/cms/templates/:id.json
Notes
Porta uses trailblazer/roar-rails to implement Representers that are used on the JSON responses.
Roar, by default, removes keys with null values from the responses, so we need to make sure we add exceptions for all nullable keys in order to respond with null.
- clones
-
-
- Closed
-
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-
-
THREESCALE-2137 Unify output format of API calls in "3scale API Documentation"
-
- Closed
-
-
THREESCALE-5715 Bring JSON API to level of XML API and possibly obsolete XML
-
- Closed
-
- mentioned on
