Hi Prashant, Usually, what you are asking is a bad idea. The idea of using a service, is to make very clear to your code, where stuff is coming from. It's more about cognitive programmer load, then that there is a technical need for it. Given that, I don't think you need an lecture on why using the global scope is bad, and there are valid reasons to use it anyway. (I have found that really valid reasons really few!) The most sane thing to do is add an wrapper component(or ngController if you want that) that exposes the model on it's scope. That way the model becomes available to everything inside the wrapper.
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.
