[MGNLCT-106] Handle most content structures when reading external content via content type Created: 13/Feb/19 Updated: 02/Apr/19 |
|
| Status: | Open |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Christopher Zimmermann | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Release notes required: |
Yes
|
| Documentation update required: |
Yes
|
| Epic Link: | External Content |
| Sprint: | Phase 2 |
| Description |
An ideal solution would work with any type of data source, but the REST use case with JSON is the most important one. Most REST API's format their content in different ways, with different wrapper nodes, and different heirarchies. Therefore developers need a flexible system to retrieve the content they are interested in. Resource: REST Response Examples Acceptance Criteria:
|