[MAGNOLIA-6930] Allow module definitions override properties coming from web app config Created: 23/Jan/17 Updated: 23/Jan/17 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.5.1 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| 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)
|
||||||||
| Description |
|
At the moment module definitions have a rather lower priority when it comes to the property resolution (e.g. if magnolia.properties contains the property - it'll be used). Because of that is is not possible to override such properties as e.g. theme or widgetset ids. I would say that the order of the property sources is already correct in our internals, we should maybe just let the AbstractMagnoliaConfigurationProperties return the last encountered property value instead of the first one. |