{ "id": "104950", "key": "ALOY-387", "fields": { "issuetype": { "id": "2", "description": "A new feature of the product, which has yet to be developed.", "name": "New Feature", "subtask": false }, "project": { "id": "11113", "key": "ALOY", "name": "Alloy", "projectCategory": { "id": "10400", "description": "Tools for developing applications", "name": "Tooling" } }, "fixVersions": [ { "id": "14770", "description": "Alloy 0.3.4", "name": "Alloy 0.3.4", "archived": false, "released": true, "releaseDate": "2012-12-14" }, { "id": "14773", "description": "2012 Sprint 24", "name": "2012 Sprint 25", "archived": true, "released": true, "releaseDate": "2012-12-17" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2012-12-12T00:07:23.000+0000", "created": "2012-11-14T15:08:47.000+0000", "priority": { "name": "Medium", "id": "3" }, "labels": [ "notable" ], "versions": [ { "id": "14631", "description": "Alloy 0.3.1", "name": "Alloy 0.3.1", "archived": false, "released": true, "releaseDate": "2012-11-02" } ], "issuelinks": [ { "id": "22783", "type": { "id": "10020", "name": "Depends", "inward": "is dependent of", "outward": "depends on" }, "inwardIssue": { "id": "103870", "key": "ALOY-343", "fields": { "summary": "Facilitate Alloy code completion in Studio", "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" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "6", "description": "gh.issue.epic.desc", "name": "Epic", "subtask": false } } } }, { "id": "22895", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "100716", "key": "TISTUD-2251", "fields": { "summary": "Support Node/NPM module loadpaths", "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" } }, "priority": { "name": "High", "id": "2" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } }, { "id": "22898", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "inwardIssue": { "id": "94654", "key": "TISTUD-1870", "fields": { "summary": "Content assist for $. in JS files", "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" } }, "priority": { "name": "Medium", "id": "3" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } } ], "assignee": null, "updated": "2018-03-07T22:26:11.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": "12331", "name": "Titanium Studio" } ], "description": "Alloy controller files, which are Javascript, need code completion support in TiStudio. Currently there is inline JSDuck documentation for a lot of Alloy's features already in its code. In order to be able to leverage this, we need to determine a few things:\r\n\r\n# Does TiStudio already support the JSDuck format? If not, could it support a subset of the format that we can adhere to when documenting Alloy for code completion?\r\n# How will TiStudio get the necessary code completion docs? Can they pull it out of the alloy source themselves or will Alloy need to provide a script or something that will generate a file, or files, that contains only the relevant JSDuck comments.\r\n# Do we need to establish code completion rules beyond what is defined in the JSDuck comments? For example, the *$* always represents the current controller, which will have access to any functions and properties in the BaseController class (which is documented). How can we convey that information to TiStudio so that it can do autocompletion in this case?\r\n\r\nAny other questions, concerns, etc... regarding code completion for Alloy controller files will be logged in this ticket.", "attachment": [], "flagged": false, "summary": "TiStudio code completion for Alloy controller files (JS)", "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": "230968", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "initial work for tistudio JS code completion has been completed from the Alloy side. Any further work necessary from Alloy to facilitate it will be documented in future tickets.", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2012-12-12T00:07:23.000+0000", "updated": "2012-12-12T00:07:23.000+0000" } ], "maxResults": 2, "total": 2, "startAt": 0 } } }