Hi Michel, app.value, is indeed the way to set values. You can indeed insert an object into value(). No problem there. But then putting the object on rootScope is kind of missing the point. If you need it available all the time, in all the places, don't bother using a .value(), and put it on the rootScope. I suspect you don't need those values everywhere, not all the time. You can inject those values everywhere you need those. It takes some getting used too, but it leads to a better separation of issues, and your code becomes more reusable. Also, it makes clear in your code where those values are coming from, and that helps during debugging and testeing.
Regards Sander -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
