[MGNLUI-6182] Once contentType file has error, changes are no longer detected Created: 03/Sep/20 Updated: 29/Sep/20 Resolved: 04/Sep/20 |
|
| Status: | Closed |
| Project: | Magnolia UI |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.3 |
| Type: | Bug | Priority: | Major |
| Reporter: | Canh Nguyen | Assignee: | Canh Nguyen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 4d | ||
| 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)
|
||||||||
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
||||||||
| Epic Link: | Content Types phase 2 | ||||||||
| Sprint: | HL & LD 10 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
Timebox for investigation: 3 SP Once a contentType file has an error which causes the app definition to be broken with a severre error, then additional changes to the contentType file will not be detected, and therefore the app will remain broken even once the error in the contentType file is fixed. The ContentTypes system should be improved so that even when an app definition has errors, any changes to the referenced contenttype files will be registered and applied - such that the app will work again, as would be expected. To reproduce
Note, there must aldready be some code to apply detected changes to contentTypes files to the apps, as when one makes changes to the CT that are valid, then the app is correctly updated.
You could use these valid files: App file CT file |