a7228cf83d
Repositories are a class of services to help with CRUD actions, most of the functionality is reused across various Models. This creates a new repository service that centralizes all this reused functionality. Inheritance via ember `Service.extend` is used as opposed to decorating via Mixins. 1. Move all repository services (and their tests) to a services/repository folder 2. Standardize on a singular name format 'node vs nodes' 3. Create a new 'repository' service to centralize functionality. This should be extended by 'repository' services
22 lines
591 B
JavaScript
22 lines
591 B
JavaScript
import RepositoryService from 'consul-ui/services/repository';
|
|
import { inject as service } from '@ember/service';
|
|
import { get } from '@ember/object';
|
|
|
|
const modelName = 'session';
|
|
export default RepositoryService.extend({
|
|
store: service('store'),
|
|
getModelName: function() {
|
|
return modelName;
|
|
},
|
|
findByNode: function(node, dc) {
|
|
return get(this, 'store').query(this.getModelName(), {
|
|
id: node,
|
|
dc: dc,
|
|
});
|
|
},
|
|
// TODO: Why Key? Probably should be findBySlug like the others
|
|
findByKey: function(slug, dc) {
|
|
return this.findBySlug(slug, dc);
|
|
},
|
|
});
|