I am a javascript noob so i dont understand why in the code below the author uses Avengers.cast instead of just Avengers?
var myApp = angular.module('myApp', []);
myApp.factory('Avengers', function() {
var Avengers = {};
Avengers.cast = [{
name: "Robert Downey Jr.",
character: "Tony Stark / Iron Man"
}];
return Avengers;
})
function AvengersCtrl($scope, Avengers) {
$scope.avengers = Avengers;
}
var Avengers = {};
This means: create a new object and refer to it by the variable Avengers
Avengers.cast = [{
name: "Robert Downey Jr.",
character: "Tony Stark / Iron Man"
}];
This means: the object just created now has a property called cast. This is an Array and contains exactly one object (with two properties with String values).
In your code, cast property of Avengers is set to specific object. Let say, initially Avengers has no value. In factory section, Avengers became
Avengers.cast = [{
name: "Robert Downey Jr.",
character: "Tony Stark / Iron Man"
}];
You can use this somewhere in your code like console.log(Avengers.cast). Following example for the function;
myApp.factory('Avengers', function() {
return {
helloWorld: function() {
return "Hello, World!"
}
};
});
You can use Avengers.helloWorld() somewhere in your code.
As summary, you can create objects with angular.js factory and set property for that object also create functions in that object. Refer here for more details
To answer your specific question: there is more than one way to pass information around.
The author could have made the Avengers service just the array instead of an object with the array.
So the choice was somewhat arbitrary, as you seem to be picking up on.
That said if the author is planning on extending the Avengers service with more properties, then that is why an object with the array was chosen.
Although if you're just going to do that you should check out constant - maybe it would be more appropriate than factory.
caston the objectAvengers. It can be accessed using the same notation.