[MAGNOLIA-6809] Add location to problem aggregation in order to know where the 'problem' originated from Created: 11/Oct/16 Updated: 09/Feb/17 Resolved: 13/Oct/16 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.5 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Philip Mundt | Assignee: | Philip Mundt |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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)
|
| Date of First Response: | |
| Sprint: | Basel 65 |
| Story Points: | 1 |
| Description |
|
Currently, there is no way to know where the problem occurred during M2B or N2B aggregation. We should add the location to DefinitionProvider.Problem and TransformationProblem in order to provide the details of where the actual problem occured. |
| Comments |
| Comment by Federico Grilli [ 13/Oct/16 ] |
|
QA: location apparently can be null (see below after Title:), as I got in my QA testing.
Severity type: SEVERE Title: null: [Definition resolution] - Parsing configuration data from [/mtk/templates/pages/basic.yaml] failed Problem details: Failed to parse YAML file: Scanner: while scanning a simple key in 'reader', line 15, column 1: areas ^ could not found expected ':' in 'reader', line 16, column 13: htmlHeader: ^ ... |