The AngularJS API provides a function named extend that can help improve your code quality and efficiency. I always look for ways to improve quality, increase efficiency, reduce risk and eliminate ritual and ceremony when I am developing software.
Perhaps the simplest way to express this is the DRY principle (Don’t Repeat Yourself). I prefer a refactoring-driven approach to this principle. Instead of trying to anticipate what might be needed in a framework, I simply evolve it and refactor when I see an opportunity to improvement. Oftentimes Angular’s extend function is a part of that refactoring.
Assume I am writing a page that allows the user to click two buttons to produce a list of categories and products. Here is a screenshot with the categories loaded and the products waiting for the user to request them.
![image_thumb[1]](https://www.webcodegeeks.com/wp-content/uploads/2015/01/image_thumb1.png)
The source for data is exposed via the example API at OData.org. To encapsulate the call for categories, I create a component and register it with Angular that looks like this:
function CategoriesService($http, $q) {
this.$http = $http;
this.$q = $q;
}
CategoriesService.prototype.get = function () {
var deferral = this.$q.defer();
this.$http.get('http://services.odata.org/V4/OData/OData.svc/')
.success(function (response) {
deferral.resolve(response.value);
})
.error(function (err) {
deferral.reject(err);
});
return deferral.promise;
};
app.service('categories', CategoriesService);Next, I move on to products. It turns out that the products service looks almost identical to the categories service! I don’t want to repeat myself so it’s time to refactor the code to take advantage of the principle of inheritance. I encapsulate the base functionality for dealing with the service in a base class, then inherit from that and specify what’s unique between products and categories. The base class looks like this:
var baseOData = {
$http: {},
$q: {},
baseUrl: 'http://services.odata.org/V4/OData/OData.svc/',
entity: '',
get: function () {
var defer = this.$q.defer();
this.$http.get(this.baseUrl + this.entity)
.success(function (response) {
defer.resolve(response.value);
})
.error(function (err) {
defer.reject(err);
});
return defer.promise;
}
};
Notice I’ve captured everything that is repeated: the base portion of the URL and the wrapper that handles the promise so the result is returned and the consuming class doesn’t have to understand how the collection is implemented in the API. The only difference I found between the categories and products is the name of the entity specified in the URL, so I expose that with a property on the base class that can be overridden by the service implementation. Using this base class I implement the category service like this:
function CategoriesService($http, $q) {
this.$http = $http;
this.$q = $q;
this.entity = 'Categories';
}
angular.extend(CategoriesService.prototype, baseOData);
app.service('categories', CategoriesService);
The shell for the categories service simply sets up the dependencies and registers the entity because the base class holds all of the common functionality. The call to extend automatically applies the properties and functions from the base definition to the category service. Notice that I am extending the prototype; this will ensure that the properties and functions are part of any instance that is created. Angular will also bind the properties and functions so this refers to the instance itself.
The products service is then implemented the same way with a different entity specified. Although I could provide a service that takes in the entity as a parameter and returns the promise (even less code), I may want to have specific properties or methods that are unique to the category and/or product implementation. I really don’t know yet so I keep them as separate components and will refactor them down to a single service if the pattern doesn’t change.
You can call extend multiple times or pass a collection of objects. This enables your components to inherit from multiple “base classes.” Another way to look at it is that you can define behaviors and apply those behaviors to the class.
I prefer the “controller as” syntax for my controller definitions. In this example the controller takes a dependency on the product and category service and exposes methods to request them that are bound to buttons. The initial implementation looked like this:
function Controller(products, categories) {
this.productService = products;
this.categoryService = categories;
this.products = [];
this.categories = [];
}
Controller.prototype.getCategories = function () {
var _this = this;
this.categoryService.get().then(function (result) {
_this.categories = result;
});
};
Controller.prototype.getProducts = function () {
var _this = this;
this.productService.get().then(function (result) {
_this.products = result;
});
};
app.controller('exampleCtrl', Controller);
Wouldn’t it be nice if to encapsulate the controller functionality in a single definition? Actually, that is possible! Using extend I simplified the declaration for my controller by combining the functions into a single object definition. I removed the initialization of the product and categories list from the constructor and moved them into a consolidated definition that looks like this:
angular.extend(Controller.prototype, {
products: [],
categories: [],
getCategories: function () {
var _this = this;
this.categoryService.get().then(function (result) {
_this.categories = result;
});
},
getProducts: function () {
var _this = this;
this.productService.get().then(function (result) {
_this.products = result;
});
}
});
This convention makes it easier to group related functionality together and ensure there is a consistent implementation of this. The implementation is very similar to the way that TypeScript handles inheritance.
As you can see, although the documentation for extend is quite simple, the functionality can be quite powerful. View the source code and full working example here.
| Reference: | Using AngularJS to Extend Your Code Quality from our WCG partner Jeremy Likness at the C#er : IMage blog. |
