Loading...

XML

Word

Printable

Type: Sub-task
Resolution: Done
Priority: Major
Fix Version/s: 2.14.0 GA
Affects Version/s: None
Component/s: Documentation, System
Labels:
- 2.14-to-test

Story Points:
5
Blocked:
False
Blocked Reason:
None
Ready:
False
3Scale PT Tested upstream:
Not Started
3scale PT Docs:
Not Started
3scale PT Product Specs:
Not Started
3scale PT Product Update Ready:
Not Started
3scale PT Released In Saas:
Not Started
3scale PT Verified Product:
Not Started
Target Release:

2.14.0 GA
Intelligence Requested:
Market:

Sprint:
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

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

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.