{ "id": "100911", "key": "ALOY-250", "fields": { "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [ { "id": "14171", "description": "", "name": "2012 Sprint 19", "archived": true, "released": true, "releaseDate": "2012-09-24" }, { "id": "14176", "description": "Release 3.0.0", "name": "Release 3.0.0", "archived": false, "released": true, "releaseDate": "2012-12-13" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2012-09-14T07:50:41.000+0000", "created": "2012-09-12T06:43:04.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [], "issuelinks": [], "assignee": null, "updated": "2018-03-07T22:25:47.000+0000", "status": { "description": "A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.", "name": "Resolved", "id": "5", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "12326", "name": "XML", "description": "View XML and parsing" } ], "description": "It seems as though XML formatting errors are being reported in the log, but not aborting the Alloy build process. For example:\r\n\r\n{code:xml}\r\n\r\n\t\r\n\t\t\r\n\t\r\n\r\n{code}\r\n\r\nThis causes the following error message to appear in the log:\r\n\r\n{code}\r\nend tag name: Window is not match the current start tagName:Window32\r\n{code}\r\n\r\nBut it does not abort the build until a later error forces it to. These XML errors should be caught when they occur and conveyed to the developer so that they can fix them before the app runs, not simply warn them and have them encounter unexpected behavior.", "attachment": [], "flagged": false, "summary": "Alloy should throw errors on XML formatting failures", "creator": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "subtasks": [], "reporter": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "environment": null, "comment": { "comments": [ { "id": "218746", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "I tracked down why we don't get exceptions on malformed XML and only warnings:\r\n\r\nhttps://github.com/jindw/xmldom/blob/master/dom-parser.js#L71\r\n\r\nI have logged and issue with xmldom, but I'm not sure how long it will take to get a change in place, if the developer wants to do it at all. We may have to consider forking and submitting a PR, or looking for a XML validator just for this purpose.\r\n\r\nhttps://github.com/jindw/xmldom/issues/36", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-09-12T16:42:45.000+0000", "updated": "2012-09-12T16:42:45.000+0000" }, { "id": "218981", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Problem solved, but logged ALOY-267 to continue work towards an even better solution.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-09-14T07:50:42.000+0000", "updated": "2012-09-14T07:50:42.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }