[MAGNOLIA-8303] Refactor magnolia-configuration module's name Created: 08/Feb/22 Updated: 09/Feb/22 Resolved: 09/Feb/22 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Martin Drápela | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 |
|
In the Configuration app, the name of the module with the following coordinates <groupId>info.magnolia.core</groupId> <artifactId>magnolia-configuration</artifactId> <name>Magnolia Configuration Framework</name> is just config: modules:
config:
config:
yamlReaderConfiguration:
maxAliasesForCollectionsInYaml: 100
In many places though, "config" is a submodular element (folder) containing module configurations in other modules (including this "config" module):
For decoration purposes and to eliminate ambiguities, I think it would be better if the module name were sth different, for example: modules:
configuration-framework:
config:
yamlReaderConfiguration:
maxAliasesForCollectionsInYaml: 100
|