[MAGNOLIA-6649] Refactor NameDefinition <-> DefinitionMetadata name binding mechanism Created: 28/Apr/16 Updated: 03/May/16 Resolved: 29/Apr/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 5.4.6 |
| Fix Version/s: | 5.4.7 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Aleksandr Pchelintcev |
| Resolution: | Fixed | Votes: | 1 |
| 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)
|
||||||||
| Sprint: | Basel 42 | ||||||||
| Story Points: | 0 | ||||||||
| Description |
|
The algorithm in question ensures consistency of the name of the definitions to which it is important (see NamedDefinition interface). Currently this mechanism consists of two parts: What is bad here?
Proposed solution: eliminate step 2) completely, do everything during step 1.
The solution is provided as a part of Related unit tests: |