[MGNLCT-174] Adapt ContentTypeRegistry to the inversion of the dependency between the registry and cfg sources Created: 26/Apr/21 Updated: 27/May/21 Resolved: 14/May/21 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Aleksandr Pchelintcev | Assignee: | Rabie Hayoun |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
[X]*
registry keeps no resolved configuration state on its own
[X]*
configuration source keeps the state of the definitions it discovered
[X]*
decoration is either discarded in PoC or (better) resolved/applied in the cfg source
[X]*
(optionally) validation can be still applied on registry level
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Epic Link: | SaaS project configuration | ||||||||||||||||
| Sprint: | Cloud Service 7, Cloud Service 8, Cloud Service 9 | ||||||||||||||||
| Story Points: | 5 | ||||||||||||||||
| Description |
|
, |