{
	"id": "113465",
	"key": "ALOY-644",
	"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": "15402",
				"description": "Alloy 1.2.0, concurrent with SDK 3.1.0",
				"name": "Alloy 1.2.0",
				"archived": false,
				"released": true,
				"releaseDate": "2013-08-15"
			},
			{
				"id": "15406",
				"description": "2013 Sprint 09",
				"name": "2013 Sprint 09",
				"archived": true,
				"released": true,
				"releaseDate": "2013-05-06"
			}
		],
		"resolution": {
			"id": "1",
			"description": "A fix for this issue is checked into the tree and tested.",
			"name": "Fixed"
		},
		"resolutiondate": "2013-04-29T16:00:39.000+0000",
		"created": "2013-04-27T01:02:49.000+0000",
		"priority": {
			"name": "Medium",
			"id": "3"
		},
		"labels": [
			"qe-testadded"
		],
		"versions": [],
		"issuelinks": [],
		"assignee": {
			"name": "tlukasavage",
			"key": "tlukasavage",
			"displayName": "Tony Lukasavage",
			"active": true,
			"timeZone": "America/Los_Angeles"
		},
		"updated": "2013-07-29T20:56:58.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": "12329",
				"name": "Runtime",
				"description": "Generic bucket for uncategorized runtime issues"
			}
		],
		"description": "Currently when no adapter type is specified in an Alloy model, one is specified by default. On Mobileweb it is the localStorage adapter, on all other it is the SQLite (sql) adapter. This behavior is confusing and undesired in many cases where the developer does not want persistence at all, but just a model to manage the current state of the app. \r\n\r\nAll default adapter types will be removed and a sync adapter with no persistence should be used instead.",
		"attachment": [],
		"flagged": false,
		"summary": "Alloy should use no persistence when no adapter type is specified",
		"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": "249358",
					"author": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "PR: https://github.com/appcelerator/alloy/pull/123\ntest case: https://github.com/appcelerator/alloy/tree/master/test/apps/testing/ALOY-644\n\nFunctional testing should show console warnings for both the {{appState.fetch()}} and {{model.save()}} calls in the index.js controller, instead of failing with a sync error exception as they did in the past. The app should function properly without persistence, changing the color and counter on the first tab and then adding the \"+\" to the end of each row on the 2nd tab. Since no persistence is being used, the models should be reset on each run.\n\nThis fix modified the central alloy.js file that affects all processing of models. In addition to asserting that the test case behaves as expected, most if not all test apps in the [models folder of the repo|https://github.com/appcelerator/alloy/tree/master/test/apps/models] should be tested to ensure that they still behave as expected. I have done this myself and they all do, but additional testing would also be beneficial.",
					"updateAuthor": {
						"name": "tlukasavage",
						"key": "tlukasavage",
						"displayName": "Tony Lukasavage",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-04-29T15:59:36.000+0000",
					"updated": "2013-04-29T15:59:36.000+0000"
				},
				{
					"id": "263742",
					"author": {
						"name": "fcasali",
						"key": "fcasali",
						"displayName": "Federico Casali",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"body": "Verified as working as expected.\nNo persistence is being used and no exception errors are raised.\n\nTitanium SDK 3.1.2.v20130726192706\nAlloy 1.2.0-alpha\nAppcelerator Studio 3.1.3.201307252418\nCLI 3.1.2\nNode 0.8.22\n\nClosing.",
					"updateAuthor": {
						"name": "fcasali",
						"key": "fcasali",
						"displayName": "Federico Casali",
						"active": true,
						"timeZone": "America/Los_Angeles"
					},
					"created": "2013-07-29T20:55:18.000+0000",
					"updated": "2013-07-29T20:55:18.000+0000"
				}
			],
			"maxResults": 2,
			"total": 2,
			"startAt": 0
		}
	}
}