As an editor, I want to use page and component variants on the same page
(MGNLPN-362)
|
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Component p13n, Integration |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.3, 1.4.2 |
| Type: | Sub-task | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Release notes required: |
Yes
|
| Documentation update required: |
Yes
|
| Date of First Response: | |
| Sprint: | Kromeriz 83 |
| Description |
|
Provide a single switch that enables page and component variants on the same page. The switch can be a configuration property but it should be a convenient single place for administrators to enable the feature. Don't require developers to decorate action availability in multiple places. |
| Comments |
| Comment by Roman Kovařík [ 06/Feb/17 ] |
|
ahietala any idea how the config property could be named? |
| Comment by Roman Kovařík [ 06/Feb/17 ] |
|
Another question: what about component variants inside of component variants? |
| Comment by Antti Hietala [ 07/Feb/17 ] |
|
To be future proof, how about allowNestedVariants. The term is open enough that we can add support for area variants and component-in-component variants later. |