framework/ember/app/adapters/application.js

import JsonApiAdapter from 'ember-json-api/json-api-adapter';
import config from '../config/environment';

export default JsonApiAdapter.extend({

	// Todo: make this loaded via an environment variable or something
	host: config.apiURL
	
});
Upgrade ember-cli to 0.1.4 and fix related breakage. closes #18 2014-12-23 10:15:07 +08:00			`import JsonApiAdapter from 'ember-json-api/json-api-adapter';`
More flexible API URL (necessary for testing) 2015-01-23 10:18:21 +08:00			`import config from '../config/environment';`
Hello world! 2014-12-20 14:26:46 +08:00
Change the way we fetch multiple posts by ID JSON-API specifies that multiple resources should be fetched with a comma-separated list of IDs, i.e. discussions/1,2,3,4. But this is problematic because if we do a findQuery with only one ID, then a single object will come back from the API where the serializer is expecting an array containing a single object. Instead, I’ve just implemented an ids “filter” on the discussions index API route (which is the default way that the adapter finds multiple IDs.) 2015-01-16 14:45:23 +08:00			`export default JsonApiAdapter.extend({`
Upgrade ember-cli to 0.1.4 and fix related breakage. closes #18 2014-12-23 10:15:07 +08:00
Change the way we fetch multiple posts by ID JSON-API specifies that multiple resources should be fetched with a comma-separated list of IDs, i.e. discussions/1,2,3,4. But this is problematic because if we do a findQuery with only one ID, then a single object will come back from the API where the serializer is expecting an array containing a single object. Instead, I’ve just implemented an ids “filter” on the discussions index API route (which is the default way that the adapter finds multiple IDs.) 2015-01-16 14:45:23 +08:00			`// Todo: make this loaded via an environment variable or something`
More flexible API URL (necessary for testing) 2015-01-23 10:18:21 +08:00			`host: config.apiURL`
Change the way we fetch multiple posts by ID JSON-API specifies that multiple resources should be fetched with a comma-separated list of IDs, i.e. discussions/1,2,3,4. But this is problematic because if we do a findQuery with only one ID, then a single object will come back from the API where the serializer is expecting an array containing a single object. Instead, I’ve just implemented an ids “filter” on the discussions index API route (which is the default way that the adapter finds multiple IDs.) 2015-01-16 14:45:23 +08:00
			`});`