[MGNLCT-70] Report when !with-type specifies a non-existant content type Created: 11/Sep/18 Updated: 20/Feb/19 Resolved: 28/Jan/19 |
|
| Status: | Closed |
| Project: | Content Types |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.1 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Christopher Zimmermann | Assignee: | Jaroslav Simak |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 0.25d | ||
| 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)
|
||||||||
| Epic Link: | Content Types finalization | ||||||||
| Sprint: | Features 3 | ||||||||
| Story Points: | 5 | ||||||||
| Description |
|
When an app definition includes a !with-type directive which specifies a non-existant content type, then a problem should be shown in the definitions app and an error should be reported in the log. Currently no problems are reported, and nothing shows up in the log. This will help developers - for example when they make a simple typo in the content type name. Acceptance criteria:
|
| Comments |
| Comment by Christopher Zimmermann [ 13/Sep/18 ] |
|
Needs research according to developers. |