{ "id": "93993", "key": "ALOY-77", "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": "14036", "description": "2012 Sprint 14", "name": "2012 Sprint 14", "archived": true, "released": true, "releaseDate": "2012-07-19" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2012-07-19T11:52:06.000+0000", "created": "2012-06-27T11:41:46.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [], "versions": [ { "id": "14036", "description": "2012 Sprint 14", "name": "2012 Sprint 14", "archived": true, "released": true, "releaseDate": "2012-07-19" } ], "issuelinks": [], "assignee": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "updated": "2014-02-04T00:34:41.000+0000", "status": { "description": "The issue is considered finished, the resolution is correct. Issues which are closed can be reopened.", "name": "Closed", "id": "6", "statusCategory": { "id": 3, "key": "done", "colorName": "green", "name": "Done" } }, "components": [ { "id": "12326", "name": "XML", "description": "View XML and parsing" } ], "description": "We will need to probably build out a system by which we can do various combinations of XML from View markup.\r\n\r\nFor example, in Ti, we have certain parent/child relationships to certain objects which need to be mapped so that its more helpful in XML. \r\n\r\nExample is a map. Ideally, you would do something like:\r\n\r\n{code:xml}\r\n\r\n \r\n\r\n{code}\r\n\r\nAs a way to statically build a map with a single annotation.\r\n\r\nAlso, in the tableview, you have a similar scenario but with additional nesting possibilities:\r\n\r\n{code:xml}\r\n\r\n \r\n \r\n \r\n\r\n{code}\r\n\r\nAlso, as in the map above, we need to also be smart about Ti builtins to make sure we auto-prefix the ns (Ti.Map vs. Ti.UI) in these cases.\r\n", "attachment": [], "flagged": false, "summary": "Support per-component tag parsing for complex relationships", "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": "201037", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "Tag-specific parsers can now be written in the {{Alloy/commands/compile/parsers}}", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-07-02T05:51:43.000+0000", "updated": "2012-07-02T05:51:43.000+0000" } ], "maxResults": 1, "total": 1, "startAt": 0 } } }