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
17 lines
440 B
JavaScript
17 lines
440 B
JavaScript
import Route from '@ember/routing/route';
|
|
import { inject as service } from '@ember/service';
|
|
import { hash } from 'rsvp';
|
|
import { get } from '@ember/object';
|
|
|
|
export default Route.extend({
|
|
repo: service('repository/dc'),
|
|
model: function(params) {
|
|
return hash({
|
|
item: get(this, 'repo').getActive(),
|
|
});
|
|
},
|
|
afterModel: function({ item }, transition) {
|
|
this.transitionTo('dc.services', get(item, 'Name'));
|
|
},
|
|
});
|