[MAGNOLIA-7282] Configurable content decorators Created: 19/Mar/18 Updated: 11/Jul/19 |
|
| Status: | Accepted |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Story Points: | 3 |
| Description |
|
Magnolia uses bunch of node decorators (for custom versioning, escaping of HTML entities, i18n, p13n...). Configurability might be useful to used dedicated wrappers only for workspace where are actually needed. Ideal solution would be to expose the configuration e.g. under core module but it might be technically demanding since the repository manager is started before modules. Since this was not needed yet, we should consider if we want to invest time or just leave with the current possibilities (hardcoded application of decorators by code) |
| Comments |
| Comment by Roman Kovařík [ 23/Mar/18 ] |
|
Blocked: decide in which version magnolia we'll need it (5.7)?. |
| Comment by Roman Kovařík [ 01/Jun/18 ] |
|
Not required by the GDPR epic anymore. |