[MGNLCT-162] Report problem in definition app if non-existing content-type is referenced Created: 22/Sep/20 Updated: 29/Oct/20 Resolved: 23/Oct/20 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Robert Šiška | Assignee: | Robert Šiška |
| Resolution: | Fixed | Votes: | 0 |
| 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: | HL & LD 12, HL & LD 13, HL & LD 14 | ||||||||
| Story Points: | 3 | ||||||||
| Description |
|
When content-type definition references non-existing content-type, no problems are registered. That causes problems in features that rely on CTs, like e.g. GraphQL schema generation or ContentType-based apps. |
| Comments |
| Comment by Robert Šiška [ 09/Oct/20 ] |
|
Reopening to fire ContentTypeChanged event in case when yaml parsing fails. To reproduce, break the syntax by e.g. adding line at top of registered content-type definition. Problem is reported in definitions app, but the event is not fired. |