Details
-
Improvement
-
Resolution: Unresolved
-
Neutral
-
None
-
5.5.1
-
None
-
None
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.
Checklists
Acceptance criteria
Attachments
Issue Links
- relates to
-
CONTEDIT-1 Cleanup and ready POC for putting it into the product
-
- Closed
-