{ "id": "174044", "key": "ALOY-1702", "fields": { "issuetype": { "id": "4", "description": "An improvement or enhancement to an existing feature or task.", "name": "Improvement", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [], "resolution": null, "resolutiondate": null, "created": "2019-08-22T09:37:15.000+0000", "priority": { "name": "None", "id": "6" }, "labels": [], "versions": [], "issuelinks": [], "assignee": null, "updated": "2019-08-22T09:37:53.000+0000", "status": { "description": "The issue is open and ready for the assignee to start work on it.", "name": "Open", "id": "1", "statusCategory": { "id": 2, "key": "new", "colorName": "blue-gray", "name": "To Do" } }, "components": [], "description": "h5.Description\r\n\r\nIn 8.2.0 we introduced support for SFSymbols and Semantic Colors, these are both accessed via methods {{Ti.UI.iOS.systemImage}} and {{Ti.UI.fetchSemanticColor}} respectively. There's no great user story currently for consuming these in XML views or TSS.\r\n\r\nI think there's 2 avenues for supporting theses, either allow their direct usage or invent a shorthand (à la {{L()}}) for them. \r\n\r\nI think it's possible that we may want to restrict {{Ti.UI.iOS.systemImage}} to TSS only though, as this needs to be gated in a version check (or maybe we can get inventive and add this to the generated code ourselves?)\r\n\r\nI'll update this ticket with some proposals after some research", "attachment": [], "flagged": false, "summary": "Improve support for SFSymbols and SemanticColor in Alloy markup", "creator": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "subtasks": [], "reporter": { "name": "eharris", "key": "eharris", "displayName": "Ewan Harris", "active": true, "timeZone": "Europe/Dublin" }, "environment": null, "comment": { "comments": [], "maxResults": 0, "total": 0, "startAt": 0 } } }