{ "id": "105764", "key": "ALOY-407", "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": [ { "id": "14634", "description": "Alloy 1.0.0", "name": "Alloy 1.0.0", "archived": false, "released": true, "releaseDate": "2013-02-19" }, { "id": "14871", "description": "2013 Sprint 02", "name": "2013 Sprint 02", "archived": true, "released": true, "releaseDate": "2013-01-28" } ], "resolution": { "id": "1", "description": "A fix for this issue is checked into the tree and tested.", "name": "Fixed" }, "resolutiondate": "2013-01-28T16:52:41.000+0000", "created": "2012-11-30T19:44:46.000+0000", "priority": { "name": "High", "id": "2" }, "labels": [ "notable" ], "versions": [ { "id": "14633", "description": "Alloy 0.3.3", "name": "Alloy 0.3.3", "archived": false, "released": true, "releaseDate": "2012-11-30" } ], "issuelinks": [ { "id": "25077", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "104831", "key": "ALOY-375", "fields": { "summary": "Alloy Model Generation providing incorrect adapter type within definition", "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": "1", "description": "A problem which impairs or prevents the functions of the product.", "name": "Bug", "subtask": false } } } }, { "id": "25078", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "105688", "key": "ALOY-402", "fields": { "summary": "Account for all 1.0.0 deprecations and API changes", "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": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } }, { "id": "23539", "type": { "id": "10003", "name": "Relates", "inward": "relates to", "outward": "relates to" }, "outwardIssue": { "id": "105749", "key": "ALOY-404", "fields": { "summary": "Create an Alloy model type that uses no persistence", "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": "Medium", "id": "3" }, "issuetype": { "id": "7", "description": "gh.issue.story.desc", "name": "Story", "subtask": false } } } } ], "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": "12332", "name": "Titanium SDK", "description": "Any integration or issues with the TiSDK" } ], "description": "h2. update (1/28/2013)\r\n\r\nThe CLI format of the generate command for models will be kept the same except for one change. The second argument that specified the adapter type is now required. Before you could do this:\r\n\r\n{code}\r\nalloy generate model myModel col1:text col2:integer\r\n{code}\r\n\r\nand it would automatically use the sql adapter. To avoid confusion, it is now required that you explicitly list the adapter type, like this:\r\n\r\n{code}\r\nalloy generate model myModel sql col1:text col2:integer\r\n{code}\r\n\r\n*NOTE:* At the time of this update, this will have no adverse effect on the TiStudio integration as TiStudio always explicitly lists the adapter type. Also, there appears to be no reference to the automatically assigned adapter type in the docs.\r\n\r\nh2. original\r\n\r\nCurrently 2 of the 3 adapters for which models can be generated (properties and localStorage) abide by a similar format:\r\n\r\n{code}\r\nalloy generate model NAME col1:type1 col2:type2 ...\r\n{code}\r\n\r\nthe sql adapter however behaves slightly differently if you specify the \"sql\" adapter explicitly in the argument list:\r\n\r\n{code}\r\nalloy generate model NAME sql col1:type1 col2:type2 ...\r\n{code}\r\n\r\nThis will create a sql adapter, and will only create a migration (necessary for execution) if the \"sql\" is put in there explicitly. Also, since the sql adapter generation is not uniform with the other commands, it causes issues when generating models for sql through TiStudio, as detailed in ALOY-375.\r\n\r\nWe need to create a standard, uniform method for creating models based on adapters. Anything that deviates from the standard should be captured in options/flags, not additional arguments. For example:\r\n\r\n{code}\r\nalloy generate model MyModel col1:string col2:int --adapter sql\r\n{code}", "attachment": [], "flagged": false, "summary": "Make \"alloy generate model\" calls uniform in format, regardless of adapter", "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": "236213", "author": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "body": "relevant changes in the *update* section of the description", "updateAuthor": { "name": "tlukasavage", "key": "tlukasavage", "displayName": "Tony Lukasavage", "active": true, "timeZone": "America/Los_Angeles" }, "created": "2013-01-28T16:52:41.000+0000", "updated": "2013-01-28T16:52:41.000+0000" } ], "maxResults": 1, "total": 1, "startAt": 0 } } }