[MGNLCT-90] Too hard to reference items from stock content apps with CT Created: 24/Jan/19 Updated: 19/Feb/19 Resolved: 30/Jan/19 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Story | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Sang Ngo Huu |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 3d | ||
| Time Spent: | 1d | ||
| Original Estimate: | 4d | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| 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
|
||||||||||||||||||||||||||||
| Date of First Response: | |||||||||||||||||||||||||||||
| Epic Link: | Content Types finalization | ||||||||||||||||||||||||||||
| Sprint: | Features 3 | ||||||||||||||||||||||||||||
| Story Points: | 8 | ||||||||||||||||||||||||||||
| Description |
|
As a developer or business analyst I want to easily add properties to my CT that reference the stock content apps, so that I can fulfull project requirements. Acceptance Criteria
Rationale:
Suggestion: Convert the key stock content apps to have the contentType class so that they can be referenced:
And in the travel demo
(But not the Contacts app. Because it is not commonly used in projects and is more of a demonstration.)
Note that all that is required is to change the class of the app, and add a contentType field. And to create a simple CT so that referencing is possible. the CT for these apps does not need to include all of the properties. Something like this will suffice: datasource: workspace: website |
| Comments |
| Comment by Sang Ngo Huu [ 24/Jan/19 ] |
|
Comment from Mika: [ So, exposing an existing app for referencing could be as "simple" as:
class: info.magnolia.ui.api.app.contenttypes.ContentTypeAppDescriptor contentType: <my-content-type> Then LinkFieldFactory should have enough information then; if that works for our selected content apps, should be easy to add to CT docs too. ] [ * From the Content Types workshop, the minimal "retrofit" content-type can be as small as: datasource: workspace: website —at least if the targeted content extends mgnl:content (worked for stories and/or pages).
|
| Comment by Sang Ngo Huu [ 30/Jan/19 ] |
|
Mark it done due to related tickets are done |