[MGNLUI-6733] Component autogeneration should allow to override template properties Created: 08/Jun/21 Updated: 08/Jun/21 |
|
| Status: | Open |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Tobias Szczepanski | 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 |
|
Currently it's only possible to define a templateId in the info.magnolia.rendering.template.AutoGenerationConfiguration. If we want to generate an exisiting Component my-component-template.yaml, which has to be not writeable/deleteable/movable/editable by editors, we have to introduce redundancy by adding a new my-component-template-not-writeable/.../editable.yaml. Please allow the AutoGenerationConfiguration to override template properties, or even define an ad-hoc template. |