@@ -67,17 +67,17 @@ __`app/js/controllers.js`.__
6767<pre>
6868...
6969
70- function PhoneListCtrl(Phone_ ) {
70+ function PhoneListCtrl(Phone ) {
7171 this.orderProp = 'age';
72- this.phones = Phone_ .query();
72+ this.phones = Phone .query();
7373}
7474//PhoneListCtrl.$inject = ['Phone'];
7575
7676
77- function PhoneDetailCtrl(Phone_ ) {
77+ function PhoneDetailCtrl(Phone ) {
7878 var self = this;
7979
80- self.phone = Phone_ .get({phoneId: self.params.phoneId}, function(phone) {
80+ self.phone = Phone .get({phoneId: self.params.phoneId}, function(phone) {
8181 self.mainImageUrl = phone.images[0];
8282 });
8383
@@ -94,7 +94,7 @@ Notice how in `PhoneListCtrl` we replaced:
9494
9595with:
9696
97- this.phones = Phone_ .query();
97+ this.phones = Phone .query();
9898
9999This is a simple statement that we want to query for all phones.
100100
@@ -116,7 +116,7 @@ We have modified our unit tests to verify that our new service is issuing HTTP r
116116processing them as expected. The tests also check that our controllers are interacting with the
117117service correctly.
118118
119- The {@link api/angular.service.$resource $resource} client augments the response object with
119+ The {@link api/angular.service.$resource $resource} service augments the response object with
120120methods for updating and deleting the resource. If we were to use the standard `toEqual` matcher,
121121our tests would fail because the test values would not match the responses exactly. To solve the
122122problem, we use a newly-defined `toEqualData` {@link
0 commit comments