[MGNLUI-4824] Control of dependencies between CTs (within one module) Created: 15/Nov/18 Updated: 30/Nov/18 Resolved: 26/Nov/18 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.7.2, 6.0 |
| Type: | Bug | Priority: | Critical |
| Reporter: | Christoph Meier | Assignee: | Mikaël Geljić |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | 0.25d | ||
| Time Spent: | 0.75d | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Content Types finalization | ||||||||
| Sprint: | Saigon 158, Saigon 159 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
The loading order of content type definitions (CTs) within one module seems unpredictable. Probably it would be more precise to say: While developing the CTs (and its apps), adding definitions step by step, one by one, there is no problem. Work arounds
Example Discussion
|
| Comments |
| Comment by Mikaël Geljić [ 24/Nov/18 ] |
|
Turns out this had little to do with dependencies between content-types: In the case above, app descriptors are loaded alphabetically. Link fields' appName values are generated against the AppDescriptorRegistry entries. In fact, link fields' appName is a mere lazy reference, and is only activated when the select button is pressed. As such, value doesn't have to be an accurate app name at registration time. There is no "definition validator" for that property either. As a bonus, |