[MGNLCT-160] Add content tagging to a content type Created: 26/Aug/20 Updated: 05/Apr/22 |
|
| 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: | tech-debt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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
|
||||||||
| Epic Link: | Content Types phase 2 | ||||||||
| Story Points: | 3 | ||||||||
| Team: | |||||||||
| Description |
|
As a Developer, I want to configure a content type such that the generated app has tagging actions. Acceptance Critiera:
Keep in mind that Content tagging is a DXCore feature, while content-types are a CE feature. Keep in mind that GraphQL creates properties based on the properties in the contentTypes - so if we add a tags property, then we need to be carefull what is generated in GraphQL since the tags property is metadata "mgnl:tags" Notes This commit demonstrates how hard and complicated it is to add tagging to a content-type based app: See
Implementation Note Implementaion will need to be split between UI (where the app generator is) and content-types module. |