[MGNLSITE-76] Define theme (imaging variations) configurations into multiple YAML files and concatenate them. Created: 06/Dec/16 Updated: 06/Dec/16 |
|
| Status: | Open |
| Project: | Magnolia Site Module |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Cédric Eberhardt | 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)
|
| Description |
|
Hello, I am currently creating web components for magnolia and I configure them as light modules. The improvement I would like to see is to be able to configure the slideshow (or any light module) variations into the yaml file saved into that light module. So that we can keep configuration in each module and not always need to copy it to one file saved in just one randomly? choosen module. For sure it can be problematic because of duplicates but maybe it can generates a compilation error or FTL duplicates, etc. I hope it was clear |